653879 – pidigin: ICQ Login protocol changed apparently - no login possible

Bug 653879 - pidigin: ICQ Login protocol changed apparently - no login possible

Summary: pidigin: ICQ Login protocol changed apparently - no login possible

Status:	RESOLVED DUPLICATE of bug 655477

Alias:	None

Product:	openSUSE 11.3
Classification:	openSUSE
Component:	GNOME (show other bugs)
Version:	Final
Hardware:	Other Other

Priority:	P5 - None Severity: Critical (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:	653852
Blocks:
	Show dependency tree / graph

Clone This Bug

Reported:	2010-11-16 08:50 UTC by Marcus Meissner
Modified:	2010-12-06 15:35 UTC (History)
CC List:	7 users (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Marcus Meissner 2010-11-16 08:50:29 UTC

+++ This bug was initially created as a clone of Bug #653852 +++

Hi,

since yesterday evening pidgin, kopete and other ICQ clients no longer log into ICQ.

apparently the login protocol got changed.

I see that e.g. Adium released a fix for it, so the change is probably known already.

we need fixes asap ;)

(perhaps just change of the login server to login.icq.com)

Comment 1 Forgotten User eDPGYP6_cn 2010-11-16 08:56:58 UTC

Changing the login server to login.icq.com leads to a "SSL Handshake failed" error if we enable SSL. So we are forced to use without SSL :(

Comment 2 Marcus Meissner 2010-11-16 08:58:19 UTC

hmm.

another ssl port? different crypto? 

i dont like to lose encryption.

Comment 3 Forgotten User eDPGYP6_cn 2010-11-16 09:08:16 UTC

The port may be different. I did not check it yet. I got sucked into some other hot-situations in day job :( As of now using without SSL, may be we need to check what port Adium uses or for some news/blogpost from icq.

Comment 4 Marcus Meissner 2010-11-16 09:08:42 UTC

kopete bug mentions slogin.icq.com  (with s in front)

Comment 5 Forgotten User eDPGYP6_cn 2010-11-16 16:48:52 UTC

(In reply to comment #4)
> kopete bug mentions slogin.icq.com  (with s in front)

I could not get it to work. It complained SSL Error and failed to connect. I am surprised that ICQ changed something so drastically without announcing anything even in their twitter feed.

Comment 6 Vincent Untz 2010-12-06 15:22:33 UTC

I guess the update to 2.7.7 (done by Luis for bug 655477) fixes this too?

Comment 7 Forgotten User eDPGYP6_cn 2010-12-06 15:30:46 UTC

(In reply to comment #6)
> I guess the update to 2.7.7 (done by Luis for bug 655477) fixes this too?

The subject says "MSN". Is there a rpm that I could test and comeback ?

Comment 8 Luis Medinas 2010-12-06 15:31:12 UTC

Yes it should fix this too (ssl problem)... i pointed the update for another pidgin ICQ bug. So this is a duplicate.

Comment 9 Luis Medinas 2010-12-06 15:33:22 UTC

(In reply to comment #7)
> (In reply to comment #6)
> > I guess the update to 2.7.7 (done by Luis for bug 655477) fixes this too?
> 
> The subject says "MSN". Is there a rpm that I could test and comeback ?

Pidgin 2.7.7 changelog
"Pidgin 2.7.7 completely fixes the MSN certificate issue, enables multiple MSN logins, and fixes the AIM SSL Handshake Failure error. 
AIM and ICQ are having server-side issues. Be patient; it should work itself out."

http://developer.pidgin.im/wiki/ChangeLog

The pidgin package submitted to Updates is the same that is available on GNOME:Apps repositories with minor changes on changelog.
You can also grab the update from 11.3:Updates:Test

Comment 10 Vincent Untz 2010-12-06 15:35:23 UTC

Okay, let's track all this in bug 655477 too, then.

*** This bug has been marked as a duplicate of bug 655477 ***