Closed GoogleCodeExporter closed 8 years ago
The same happened to me using prpltwtr 0.8.0. Deleting api.twitter.com from the
certificates list and re-adding it with the next popup did not stop the
dialogue from popping up.
Original comment by Drah...@googlemail.com
on 18 Jul 2011 at 5:28
It seems to be related to my having enabled HTTPS for my Twitter account.
Disabling https seems to have made the error go away, though that makes sense,
as it's not secure anymore...still not a perfect fix.
Original comment by Gizmokid...@gmail.com
on 18 Jul 2011 at 6:31
I wonder if it could be related to the same thing the other twitter plugin is
seeing:
https://code.google.com/p/microblog-purple/issues/detail?id=248
I don't have this issue; can you try adding
http://www.geotrust.com/resources/root_certificates/certificates/Equifax_Secure_
Global_eBusiness_CA-1.cer to your pidgin/ca-certs directory? It may be related
to a missing root CA.
Original comment by mikeage
on 19 Jul 2011 at 2:44
Scratch that: it's not the Equifax certificate (at least not with the issues
I've been seeing)
I think that installing the "Root 2 - GeoTrust Global CA" certificate from
http://www.geotrust.com/resources/root-certificates/ in pidgin/ca-certs (on
windows; not sure of the equivalent Linux directory) has solved this. Can the
OP confirm?
Original comment by mikeage
on 2 Aug 2011 at 5:37
I've been getting similar pop ups, only from search.twitter.com
Common name: *.twitter.com
Fingerprint (SHA1): 59:3f:87:4d:e3:5c:49:a1:a4:f7:8a:14:3c:79:e5:8f:03:2c:f9:92
Activation date: Sun Jul 17 12:13:11 2011
Expiration date: Tue Sep 17 19:59:59 2013
(using pidgin 2.9.0 and prpltwtr 0.10.0)
I tried saving the "GeoTrust Global CA (Base-64 encoded X.509)" cer file and
adding it via Pidgin's Tools->Certificates menu, but still getting them
Original comment by kenji...@gmail.com
on 5 Aug 2011 at 2:16
Hmmm. I downloaded the 1st link, renamed to .pem [but that's irrelevant], and
copied it to pidgin/ca-certs. That seems to have solved it. Is that the same
thing that Tools->Certificates does?
Original comment by mikeage
on 5 Aug 2011 at 2:26
I believe so, tools->certs adds the file to the users .pidgin/certificates/x509
directory
Original comment by kenji...@gmail.com
on 5 Aug 2011 at 4:12
This appears to have been resolved a long time ago.
Original comment by mikeage
on 6 Jun 2012 at 12:25
Original issue reported on code.google.com by
Gizmokid...@gmail.com
on 18 Jul 2011 at 1:20Attachments: