AIM Secure Login

[Zachary West]

On Thu, Jan 14, 2010 at 17:39, Colin Barrett <colin at springsandstruts.com>wrote:

> On Jan 13, 2010, at 9:29 AM, Zachary West wrote:
>
> > The only version of Adium with clientLogin enabled is the nightly. The
> libpurple devs are very much aware of the issue, since their release product
> ships with it enabled.
>
> Anything we can do to help?
>
> -Colin
>

It looks like the AOL servers are super-broken. Quoting a mail to Pidgin's
development list:

"Matthew Goldstein (austein on IRC) figured out why trying to use the
startOSCARSession method was failing with a signature error when tried to
use over SSL (which would work around the server complaining that we try to
set useTLS=1 over http).  In short, the signature needs to use the URL "
https://api.oscar.aol.com:80/.. <https://api.oscar.aol.com:80/>.", while
still connecting to port 443.

I wasn't comfortable committing this because I'm concerned that it would
just break again if the servers are fixed to use the correct URL in the
signature generation (or rather, no port at all, as the online docs
indicate)."

You can disable SSL for now in the nightly until it's fixed on either AOL's
or libpurple's end.

-- 
Zachary West
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20100114/78f1cd4d/attachment-0002.html>