[Pidgin] #9264: New twitter.com SSL certificate root server unrecognized

[Pidgin]

#9264: New twitter.com SSL certificate root server unrecognized
--------------------------------------------------------+-------------------
 Reporter:  zxinn                                       |        Owner:  lschiere    
     Type:  enhancement                                 |       Status:  closed      
Milestone:                                              |    Component:  unclassified
  Version:  2.5.6                                       |   Resolution:  invalid     
 Keywords:  twitter mbpurple certificate ssl microblog  |  
--------------------------------------------------------+-------------------

Comment(by bazzargh):

 projekt21: can you be a bit clearer what you tried here. Are you saying
 you added the twitter cert or the equifax cert? And are you using the
 latest pidgin/mbpurple? On what platform? Also, which certificate is it
 complaining about - I see two from twitter, the problematic one (for which
 pidgin had no CA cert) had signature:
 2b:66:47:fe:49:7d:f1:52:96:d2:42:29:cb:cb:5d:b1:db:a1:e4:fb

 I just tried this again, removing my cached certificates in case that was
 masking your problem. Those are stored in:
 C:\Documents and Settings\<user>\Application
 Data\.purple\certificates\x509\tls_peers\

 I then restarted pidgin using 'pidgin -d > debug.log', am attaching the
 relevant section showing the twitter cert being verified.

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