Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 305915 - net-im/pidgin error using ssl to icq network
Summary: net-im/pidgin error using ssl to icq network
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Net-im project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-19 17:27 UTC by Marcus Becker
Modified: 2010-02-25 06:11 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge_info.txt,3.62 KB, text/plain)
2010-02-20 19:55 UTC, Marcus Becker
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Becker 2010-02-19 17:27:32 UTC
As of today, if ssl excryption is enabled to use icq network I get the following error:

Received unexpected response from http://api.oscar.aol.com/aim/startOSCARSession: useTLS=1 is not allowed for non secure requests.

if I disabled "use SSL" in the advanced settings for the account, it works fine.
They must have changed something on their end (I guess)

Reproducible: Always

Steps to Reproduce:
1.use Pidgin ssl with icq
2.try to connect
3.

Actual Results:  
error: Received unexpected response from http://api.oscar.aol.com/aim/startOSCARSession: useTLS=1 is not allowed for non secure requests.

Expected Results:  
connection

disi-desktop ~ # pidgin --version
Pidgin 2.6.6 (libpurple 2.6.6)

same happens with 2.6.5

emerge --info: http://nopaste.info/d21b80e132.html
Comment 1 Patrick Lauer gentoo-dev 2010-02-20 18:13:17 UTC
Please don't use pastebins in bugreports.
They expire and no one knows what was supposed to be there ...
Comment 2 Marcus Becker 2010-02-20 19:55:51 UTC
Created attachment 220533 [details]
emerge --info
Comment 3 Peter Volkov (RETIRED) gentoo-dev 2010-02-25 06:11:56 UTC
Thank you for report. Yes, to workaround this issue it's possible to unset "Use clientLogin" in account options. That said, this is known problem[1] and currently resolution is not evident - this looks like aol is changing something and while this will be settled somehow I'm not sure what can be done here. Closing this bug until there will be something to do for us.

[1] http://developer.pidgin.im/ticket/11142