Unable to connect to AIM, claims SSL/TLS certificate validation error

Bug #875783 reported by Andrew Clunis
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
telepathy-haze (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Here are the relevant lines from the haze log:

purple/oscar-INFO: 11-10-16 11:26:24.788955: oscar_login: gc = 0x998200
purple/util-MESSAGE: 11-10-16 11:26:24.789019: requesting to fetch a URL
purple/dnsquery-MESSAGE: 11-10-16 11:26:24.811717: Performing DNS lookup for api.screenname.aol.com
purple/account-MESSAGE: 11-10-16 11:26:24.811876: Connecting to account orospakr.
purple/dns-WARNING: 11-10-16 11:26:24.831794: Wait for DNS child 26213 failed: No child processes
purple/dns-MESSAGE: 11-10-16 11:26:24.833233: Created new DNS child 26234, there are now 1 children.
purple/dns-MESSAGE: 11-10-16 11:26:24.833424: Successfully sent DNS request to child 26234
purple/dns-MESSAGE: 11-10-16 11:26:24.879461: Got response for 'api.screenname.aol.com'
purple/dnsquery-MESSAGE: 11-10-16 11:26:24.879560: IP resolved for api.screenname.aol.com
purple/proxy-MESSAGE: 11-10-16 11:26:24.879611: Attempting connection to 64.12.173.137
purple/proxy-MESSAGE: 11-10-16 11:26:24.879668: Connecting to api.screenname.aol.com:443 with no proxy
purple/proxy-MESSAGE: 11-10-16 11:26:24.879766: Connection in progress
purple/proxy-MESSAGE: 11-10-16 11:26:24.922674: Connecting to api.screenname.aol.com:443.
purple/proxy-MESSAGE: 11-10-16 11:26:24.922779: Connected to api.screenname.aol.com:443.
purple/nss-MESSAGE: 11-10-16 11:26:24.971626: subject=CN=api.screenname.aol.com,OU=Terms of use at www.verisign.com/rpa (c)05,OU=Core Services,O=AOL LLC.,L=Dulles,ST=Virginia,C=US issuer=OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign,OU=VeriSign International Server CA - Class 3,OU="VeriSign, Inc.",O=VeriSign Trust Network
purple/nss-MESSAGE: 11-10-16 11:26:24.971966: subject=OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign,OU=VeriSign International Server CA - Class 3,OU="VeriSign, Inc.",O=VeriSign Trust Network issuer=OU=Class 3 Public Primary Certification Authority,O="VeriSign, Inc.",C=US
purple/nss-MESSAGE: 11-10-16 11:26:24.972356: subject=OU=Class 3 Public Primary Certification Authority,O="VeriSign, Inc.",C=US issuer=OU=Class 3 Public Primary Certification Authority,O="VeriSign, Inc.",C=US
purple/certificate/x509/tls_cached-MESSAGE: 11-10-16 11:26:24.972419: Starting verify for api.screenname.aol.com
purple/certificate/x509/tls_cached-MESSAGE: 11-10-16 11:26:24.972465: Checking for cached cert...
purple/certificate/x509/tls_cached-WARNING: 11-10-16 11:26:24.972541: ...Not in cache
purple/certificate-MESSAGE: 11-10-16 11:26:24.972596: Checking signature chain for uid=CN=api.screenname.aol.com,OU=Terms of use at www.verisign.com/rpa (c)05,OU=Core Services,O=AOL LLC.,L=Dulles,ST=Virginia,C=US
purple/certificate-MESSAGE: 11-10-16 11:26:24.972793: ...Good signature by OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign,OU=VeriSign International Server CA - Class 3,OU="VeriSign, Inc.",O=VeriSign Trust Network
purple/certificate-MESSAGE: 11-10-16 11:26:24.972944: ...Good signature by OU=Class 3 Public Primary Certification Authority,O="VeriSign, Inc.",C=US
purple/certificate-MESSAGE: 11-10-16 11:26:24.972992: Chain is VALID
purple/certificate/x509/tls_cached-MESSAGE: 11-10-16 11:26:24.973042: Checking for a CA with DN=OU=Class 3 Public Primary Certification Authority,O="VeriSign, Inc.",C=US
purple/certificate/x509/tls_cached-MESSAGE: 11-10-16 11:26:24.973093: Also checking for a CA with DN=OU=Class 3 Public Primary Certification Authority,O="VeriSign, Inc.",C=US
haze/haze-DEBUG: 11-10-16 11:26:24.974100: haze_notify_message: error: SSL Certificate Error
haze/haze-DEBUG: 11-10-16 11:26:24.974154: haze_notify_message: Unable to validate certificate
haze/haze-DEBUG: 11-10-16 11:26:24.974198: haze_notify_message: The certificate for api.screenname.aol.com could not be validated. The certificate chain presented is invalid.
purple/certificate-CRITICAL: 11-10-16 11:26:24.974241: Failed to verify certificate for api.screenname.aol.com
purple/connection-MESSAGE: 11-10-16 11:26:24.974302: Connection error on 0x998200 (reason: 0 description: Error requesting https://api.screenname.aol.com/auth/clientLogin: Unable to connect to api.screenname.aol.com: SSL peer presented an invalid certificate)
haze/haze-DEBUG: 11-10-16 11:26:24.974415: close_all: closing im channels
purple/account-MESSAGE: 11-10-16 11:26:25.16468: Disconnecting account orospakr (0x74ae60)
purple/connection-MESSAGE: 11-10-16 11:26:25.16542: Disconnecting connection 0x998200
purple/oscar-MESSAGE: 11-10-16 11:26:25.16707: Signed off.
purple/connection-MESSAGE: 11-10-16 11:26:25.16769: Destroying connection 0x998200
haze/haze-DEBUG: 11-10-16 11:26:25.16882: haze_connection_dispose: disposing of (HazeConnection *)0x754170
haze/haze-DEBUG: 11-10-16 11:26:25.16937: close_all: closing im channels
haze/haze-DEBUG: 11-10-16 11:26:25.17055: haze_connection_finalize: deleting account orospakr
purple/account-MESSAGE: 11-10-16 11:26:25.17129: Destroying account 0x74ae60
purple/util-MESSAGE: 11-10-16 11:26:29.544430: Writing file accounts.xml to directory /tmp/haze-1S5Inu
purple/util-MESSAGE: 11-10-16 11:26:29.544538: Writing file /tmp/haze-1S5Inu/accounts.xml

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: telepathy-haze 0.5.0-1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Sun Oct 16 11:24:34 2011
ProcEnviron:
 LC_CTYPE=en_CA.UTF-8
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/zsh
SourcePackage: telepathy-haze
UpgradeStatus: Upgraded to oneiric on 2011-10-15 (0 days ago)

Revision history for this message
Andrew Clunis (orospakr) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in telepathy-haze (Ubuntu):
status: New → Confirmed
Revision history for this message
Ross Patterson (rossp) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.