[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 medians):

 Replying to [comment:3 bazzargh]:
 > The problem is that pidgin ships on some platforms with a relatively
 incomplete set of root CA certificates. On platforms where pidgin is built
 with system-certificate support, a more comprehensive set is available;
 but on windows, only the pidgin-supplied root CAs are used.
 >
 > This same problem also affects the facebook plugin (and it's the same
 root CA that's missing, apparently). I've attached the copy of the missing
 root CA cert I used to fix the problem for myself - by exporting it from
 firefox, and adding it into C:\Program Files\Pidgin\ca-
 certs\EquifaxSecureGlobaleBusinessCA-1.pem ; posting this info for people
 who find themselves reading this bug. It'd be a good idea for you to
 export the certificate from firefox yourself, rather than use the attached
 copy however.

 I'm still not sure how to export this file, and where exactly to put it,
 if I were even able to. The new certificate attachment isn't really even a
 file, available for download, but a link to a page in the Pidgin web page
 (as I'm sure you're well aware). I'm hardly a techy, so this all kind of
 looks like programmer jargon to me. Ha.

 Could you walk me through exactly what it takes to fix this bug, and in
 plain English, step by step? Otherwise, I don't think I'll ever figure
 this out. Or, if you're involved in developing mbpurple, just release an
 update that has this bug already smoothed out. :)

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