FS#33899 - [openssl] Empathy/Telepathy fails to work with openssl 1.0.1.e

Attached to Project: Arch Linux
Opened by Eric Renfro (psi-jack) - Sunday, 17 February 2013, 05:10 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 02 November 2013, 20:44 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Empathy with current Telepathy packages fail to authenticate with openssl 1.0.1.e, but works with openssl 1.0.1.d

Additional info:
* empathy 3.6.3-1
* telepathy-farstream 0.6.0-1
* telepathy-gabble 0.17.2-1
* telepathy-glib 0.20.1-1
* telepathy-haze 0.6.0-2
* telepathy-idle 0.1.14-1
* telepathy-logger 0.6.0-1
* telepathy-mission-control 5.14.0-1
* telepathy-rakia 0.7.4-1
* telepathy-salut 0.8.1-1

Steps to reproduce:
Try to use Empathy with openssl 1.0.1.e and create an account for AIM and/or FaceBook, authentication will fail.
Try to use Empathy with openssl 1.0.1.d and create an account for AIM and/or FaceBook, authentication will succeed.
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Saturday, 02 November 2013, 20:44 GMT
Reason for closing:  Not a bug
Comment by Pierre Schmitz (Pierre) - Sunday, 17 February 2013, 10:45 GMT
Which version of openssl did you test exactly? Version 1.0.1.e-2 should work around some more issues with broken servers.
Comment by Eric Renfro (psi-jack) - Sunday, 17 February 2013, 17:10 GMT
1.0.1.e-1 specifically. Which is wierd, because after I had downgraded back to 1.0.1.d-1, created my accounts, and later re-upgraded to 1.0.1.e-1, it was working, partially. As in, I could actually login. I think the problem was during the initial creation/validation of the accounts, it wouldn't permit it to continue because of SSL issue.

Even still, I have FaceBook included, and it keeps prompting for untrusted self-signed cert, but it's not self-signed, it's a DigiCert signed cert, so something's wrong with openssl still.
Comment by Pierre Schmitz (Pierre) - Saturday, 02 November 2013, 20:44 GMT
I cannot do anything about this here. This might be related to some networking issues related to using TLS1.2.

Loading...