Re: AIM login
Thanks Crystal. I don't believe the pidgin team made any additional changes, so I assume you found a way to work around the issue below? > On Apr 11, 2017, at 11:52 AM, Crystal Birnie > wrote: > > Confirmed. The change was made. > > Sent from my iPhone > >> On Apr 11, 2017, at 11:40 AM, Mark Zeldis wrote: >> >> >> Donald, >> >> Can you confirm that you made the change last night? I believe that the MD5 >> login (and AIM 7.5) are gone. >> >> Pidgin appears to be working still. I guess there was no issue after all? >> Are we good going forward? >> >> Thanks everyone. >> >> -Mark Zeldis >> >> >>> On Thu, Apr 6, 2017 at 9:05 AM, Donald Le wrote: >>> Eio et al, >>> >>> I was able to verify with Pidgin 2.12.0, startOSCARSession has the correct >>> info distId=1715&f=xml&k=do1UCeb5gNqxB1S1 but they were not passed through >>> our rules. >>> >>> Could you add to imApp=Pidgin/2.12.0 the devID? It should read: >>> Pidgin/2.12.0 key=do1UCeb5gNqxB1S1. >>> >>> Our trace log should read: Got FLAP CLIENT IDENTITY Pidgin/2.12.0 >>> key=do1UCeb5gNqxB1S1 >>> Note:...2.12.0(space)key... >>> >>> >>> Thanks, >>> >>> Donald Le >>> Product Management and Support AIM Platform >>> O: 703-265-5645 | M: 703-678-1073 >>> AIM: donald...@teamaol.com >>> AOL Inc. 22070 Broderick Drive Dulles, VA 20166 >>> >>>> On Mon, Apr 3, 2017 at 10:49 PM, Eion Robb wrote: >>>> Hi Donald, >>>> >>>> We've heard through a few of our support channels that you're still seeing >>>> people not using the correct details when they're logging into AIM from >>>> Pidgin. >>>> >>>> Dequis emailed you last month with the urls that we're fetching that are >>>> indeed showing distId=1715 and devId=do1UCeb5gNqxB1S1 - he also asked if >>>> you could send through the details of your Pidgin version that you were >>>> testing with. >>>> >>>> Are you able to confirm which auth URLs we should be using so we can try >>>> track down why you're not seeing the updated distId/devId? >>>> >>>> Cheers, >>>> Eion >>>> >>>>> On 14 March 2017 at 05:01, dequis wrote: >>>>> Hi, can confirm that finch is fixed now, thank you! >>>>> >>>>> That issue with pidgin 2.12.0 is really odd! I just tested both windows >>>>> installers (online and offline) and they seem fine. We did have one user >>>>> reporting a similar issue, but we couldn't reproduce it or explain it. >>>>> >>>>> Please verify the version with buddy list -> help menu -> about, the >>>>> first line should say "Pidgin 2.12.0 (libpurple 2.12.0)" followed by >>>>> "unknown". Also, help menu -> plugin information should say 2.12.0 for >>>>> the AIM plugin. That kind of mixup is rare but who knows! >>>>> >>>>> You can also enable extra debug by opening cmd.exe and doing "set >>>>> PURPLE_UNSAFE_DEBUG=1" before executing pidgin. >>>>> >>>>> Then open help menu -> debug window and connect the account. This is what >>>>> I get: >>>>> >>>>>> [...] >>>>>> (12:27:52) certificate: Successfully verified certificate for >>>>>> api.screenname.aol.com >>>>>> (12:27:52) util: Request: 'POST /auth/clientLogin HTTP/1.0 >>>>>> Connection: close >>>>>> Accept: */* >>>>>> Content-Type: application/x-www-form-urlencoded; charset=UTF-8 >>>>>> Content-Length: 85 >>>>>> >>>>>> devId=do1UCeb5gNqxB1S1&f=xml&pwd=[password]&s=dx%40dxzone.com.ar' >>>>>> (12:27:53) util: Response headers: 'HTTP/1.1 200 OK >>>>>> [...] >>>>>> (12:27:53) util: requested to fetch >>>>>> (https://api.oscar.aol.com/aim/startOSCARSession?a=[access >>>>>> token]&distId=1715&f=xml&k=do1UCeb5gNqxB1S1&ts=1489418868&useTLS=1&sig_sha256=[signature]), >>>>>> full=1, user_agent=((null)), http11=0 >>>>> >>>>> >>>>> So as far as I can see everything
Re: AIM login
Donald, Can you confirm that you made the change last night? I believe that the MD5 login (and AIM 7.5) are gone. Pidgin appears to be working still. I guess there was no issue after all? Are we good going forward? Thanks everyone. -Mark Zeldis On Thu, Apr 6, 2017 at 9:05 AM, Donald Le wrote: > Eio et al, > > I was able to verify with Pidgin 2.12.0, startOSCARSession has the correct > info *distId=1715&f=xml&k=do1UCeb5gNqxB1S1 *but they were not passed > through our rules. > > Could you add to imApp=Pidgin/2.12.0 the devID? It should read: > Pidgin/2.12.0 key=do1UCeb5gNqxB1S1. > > Our trace log should read: > *Got FLAP CLIENT IDENTITY Pidgin/2.12.0 key=do1UCeb5gNqxB1S1* > Note:...2.12.0(space)key... > > > Thanks, > > > *Donald Le* > *Product Management and Support AIM Platform* > *O*: 703-265-5645 <(703)%20265-5645> | *M*: 703-678-1073 > <(703)%20678-1073> > *AIM*: donald...@teamaol.com > *AOL Inc**. 22070 Broderick Drive Dulles, VA 20166* > > On Mon, Apr 3, 2017 at 10:49 PM, Eion Robb wrote: > >> Hi Donald, >> >> We've heard through a few of our support channels that you're still >> seeing people not using the correct details when they're logging into AIM >> from Pidgin. >> >> Dequis emailed you last month with the urls that we're fetching that are >> indeed showing distId=1715 and devId=do1UCeb5gNqxB1S1 - he also asked if >> you could send through the details of your Pidgin version that you were >> testing with. >> >> Are you able to confirm which auth URLs we should be using so we can try >> track down why you're not seeing the updated distId/devId? >> >> Cheers, >> Eion >> >> On 14 March 2017 at 05:01, dequis wrote: >> >>> Hi, can confirm that finch is fixed now, thank you! >>> >>> That issue with pidgin 2.12.0 is really odd! I just tested both windows >>> installers (online and offline) and they seem fine. We did have one user >>> reporting a similar issue, but we couldn't reproduce it or explain it. >>> >>> Please verify the version with buddy list -> help menu -> about, the >>> first line should say "Pidgin 2.12.0 (libpurple 2.12.0)" followed by >>> "unknown". Also, help menu -> plugin information should say 2.12.0 for the >>> AIM plugin. That kind of mixup is rare but who knows! >>> >>> You can also enable extra debug by opening cmd.exe and doing "set >>> PURPLE_UNSAFE_DEBUG=1" before executing pidgin. >>> >>> Then open help menu -> debug window and connect the account. This is >>> what I get: >>> >>> [...] >>>> (12:27:52) certificate: Successfully verified certificate for >>>> api.screenname.aol.com >>>> (12:27:52) util: Request: 'POST /auth/clientLogin HTTP/1.0 >>>> Connection: close >>>> Accept: */* >>>> Content-Type: application/x-www-form-urlencoded; charset=UTF-8 >>>> Content-Length: 85 >>>> >>>> devId=do1UCeb5gNqxB1S1&f=xml&pwd=[password]&s=dx%40dxzone.com.ar' >>>> (12:27:53) util: Response headers: 'HTTP/1.1 200 OK >>>> [...] >>>> (12:27:53) util: requested to fetch (https://api.oscar.aol.com/aim >>>> /startOSCARSession?a=[access token]&distId=1715&f=xml&k=do1 >>>> UCeb5gNqxB1S1&ts=1489418868&useTLS=1&sig_sha256=[signature]), full=1, >>>> user_agent=((null)), http11=0 >>>> >>> >>> So as far as I can see everything is fine. I hope that helps narrow it >>> down. >>> >>> By the way, is the message supposed to be shown on every login from a >>> legacy auth method? I don't see it when I intentionally set pidgin to >>> connect to "login.oscar.aol.com" with "don't use encryption" and >>> "MD5-based" - it just succeeds without complaining. >>> >>> By the way, slogin.oscar.aol.com is down but login.oscar.aol.com isn't. >>> I thought slogin.oscar.aol.com was supposed to die at the end of this >>> month. I think that's breaking adium (mac OS X pidgin derivative) and we >>> still haven't managed to contact their devs to fix it. So what is the fate >>> of slogin supposed to be? >>> >>> Thanks. >>> >>> On 13 March 2017 at 09:38, Donald Le wrote: >>> >>>> Hi again, >>>> >>>> I download Pidgin 2.12.0 and test login. >>>> >>>> The &q
