[Pidgin] #12906: Unable to validate certificate

[Pidgin]

#12906: Unable to validate certificate
---------------------+------------------------------------------------------
 Reporter:  Anthara  |        Owner:  QuLogic
     Type:  defect   |       Status:  new    
Milestone:           |    Component:  MSN    
  Version:  2.7.5    |   Resolution:         
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by johnroberts):

 If we name (above) servers, server "good" and server "bad",
 it seems that manually placing the omega.contacts.msn.com
 certificate from the "bad" server on the cache
 (/home/user/.purple/certificates/x509/tls_peers/...)
 - temporarily at least - solves the problem as GnuTLS validates it
 even if the certificate chain is malformed.
 But this is only a stop-gap because if on another login attempt
 Pigdin tries to connect to the "good" server, I suppose that
 the omega.contacts.msn.com from this server will replace
 the previous one, so GnuTLS will fail on the next attempt
 to the "bad" server...

 Both certificates can be obtained (with plenty of patience though...)
 through Firefox trying to connect to https://omega.contacts.msn.com

 The certificate of the "good" server has this SHA1 fingerprint:
 c8:f3:b1:69:52:36:07:33:b5:02:1b:a2:b2:b4:ce:32:b9:68:37:36

 and the "bad" server this fingerprint:
 ac:7e:e4:5f:97:b8:7e:f0:0b:ac:a6:51:9f:ba:51:f0:ad:73:17:8b

-- 
Ticket URL: <http://developer.pidgin.im/ticket/12906#comment:103>
Pidgin <http://pidgin.im>
Pidgin