Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#12948 closed defect (fixed)

AIM default settings results in SSL Handshake error

Reported by: ben_p Owned by: rekkanoryo
Milestone: 2.7.7 Component: AIM
Version: 2.7.6 Keywords:
Cc: dalekmediator

Description

Immediately after the upgrade from 2.7.5 to 2.7.6 I receive an error when connecting to AIM accounts. The error is:

Unable to connect to authentication server. SSL Handshake Failed

To resolve the issue I can modify my account by clicking the Advanced tab and changing Connection security: from "Use encryption if available" to "Don't use encryption"

This work-around was confirmed to work by another user in #pidgin on IRC.

Attachments (1)

purple-debug.log (3.7 KB) - added by ben_p 9 years ago.
Debug log from AIM connection via Debug Window

Download all attachments as: .zip

Change History (17)

comment:1 Changed 9 years ago by Robby

Ticket #12949 has been marked as a duplicate of this ticket.

comment:2 Changed 9 years ago by Robby

  • Status changed from new to pending

Please follow the instructions to get a debug log and attach it to this ticket.

comment:3 Changed 9 years ago by Robby

  • Component changed from unclassified to AIM

comment:4 Changed 9 years ago by datallah

Ticket #12950 has been marked as a duplicate of this ticket.

comment:5 Changed 9 years ago by datallah

Ticket #12952 has been marked as a duplicate of this ticket.

Changed 9 years ago by ben_p

Debug log from AIM connection via Debug Window

comment:6 Changed 9 years ago by ben_p

  • Status changed from pending to new

Attachment (purple-debug.log) added by ticket reporter.

comment:8 Changed 9 years ago by ben_p

I couldn't get the instructions at http://developer.pidgin.im/wiki/TipsForBugReports to work for me (couldn't find the log file on my Windows 7 x64 machine), but I was able to save the contents of Help -> Debug Window so hopefully that will work.

comment:9 follow-up: Changed 9 years ago by rcsheets

I have observed that checking the "Use clientLogin" box was also an effective workaround, at least for me.

comment:10 in reply to: ↑ 9 Changed 9 years ago by ben_p

Replying to rcsheets:

I have observed that checking the "Use clientLogin" box was also an effective workaround, at least for me.

I can confirm that checking "Use clientLogin" worked for me as well, even with the Connection security option set to "Require encryption".

comment:11 Changed 9 years ago by silekonn

Can confirm this bug.

comment:12 Changed 9 years ago by rekkanoryo@…

  • Milestone set to 2.7.7
  • Resolution set to fixed
  • Status changed from new to closed

(In b21beb71827799eec3525c256f12e609d91e6e4f):
Properly handle an AIM login server of login.messaging.aol.com. Fixes #12948.

comment:13 Changed 9 years ago by Robby

Ticket #12960 has been marked as a duplicate of this ticket.

comment:14 Changed 9 years ago by deryni

If you are currently using login.messaging.aol.com as the server for your account switching to login.oscar.aol.com should allow the connection to work correctly with SSL.

comment:15 Changed 9 years ago by deryni

Ticket #12961 has been marked as a duplicate of this ticket.

comment:16 Changed 9 years ago by rekkanoryo

Ticket #12971 has been marked as a duplicate of this ticket.

comment:17 Changed 9 years ago by rekkanoryo@…

(In 9fe7b6c4c4d9a15fc87bae6aa6b6521af0a0dca2):
Apply my specific AIM login fix listed below to the 2.7.7 branch.

* Plucked b21beb71827799eec3525c256f12e609d91e6e4f (rekkanoryo@…): Properly handle an AIM login server of login.messaging.aol.com. Fixes #12948.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!