Is there any particular reason that pidgin doesn't use the existing
Windows certificate store? This would seem to alleviate the need to
juggle with certificates manually.
Or did I miss part of the plot here?
On 2018-01-07 13:36, Eion Robb wrote:
https://textslashplain.com/2017/10/23/google-internet-authority-g3/ has
some info about the new Root CA and Intermediate CA certs that Google
are rolling out. On Pidgin on Windows we don't include the new "Google
Trust Services" ca-cert, so it'll keep bugging you about it
On 7 January 2018 at 04:52, Phil Smith III <[email protected]
<mailto:[email protected]>> wrote:
And they came back in the evening, though they're gone again now.
Very weird. Well, maybe not: if it's ONE server, maybe load is
higher in the evening, so that server gets pressed into action, goes
idle eventually? If there's some sort of client-server persistence,
then that might continue until that server goes idle again and gets
dropped from the cluster. Of course I'm making this up as I go
along, but it does fit the symptoms...
-----Original Message-----
From: [email protected] <mailto:[email protected]>
[mailto:[email protected] <mailto:[email protected]>]
Sent: Friday, January 05, 2018 5:27 PM
To: Phil Smith III <[email protected] <mailto:[email protected]>>;
Pidgin <[email protected] <mailto:[email protected]>>
Subject: Re: "Unable to validate certificate"
I am still getting those popups.
Why wouldn't Pidgin remember the accepted certificate?
On 05/01/2018 10:04 PM, Phil Smith III wrote:
> Saw that, but it *seems* slightly different.
>
> Weirdly, after getting them all evening and night (based on the
number of popups I had to close!), I got a few throughout the
morning and then they stopped. So maybe it really was a Google
problem--maybe one server behind a LB with a bad cert?
>
> -----Original Message-----
> From: [email protected] <mailto:[email protected]>
[mailto:[email protected] <mailto:[email protected]>]
> Sent: Friday, January 05, 2018 2:57 PM
> To: phs3stuff <[email protected] <mailto:[email protected]>>;
[email protected] <mailto:[email protected]>
> Subject: Re: "Unable to validate certificate"
>
> Similar issue here:
>
> The certificate for 0.client-channel.google.com
<http://0.client-channel.google.com> could not be validated.
> The certificate is not trusted because no certificate that
can verify it is currently trusted.
>
> There's an issue on Bitbucket:
>
https://bitbucket.org/EionRobb/purple-hangouts/issues/168/certificate-issues
<https://bitbucket.org/EionRobb/purple-hangouts/issues/168/certificate-issues>
>
>
> On 05/01/2018 3:48 PM, phs3stuff wrote:
>> After running flawlessly for a while, I'm suddenly getting:
>>
>> Unable to validate certificate
>>
>> The certificate for clients6.google.com
<http://clients6.google.com> could not be validated. The certificate
chain presented is invalid.
>>
>> This happens repeatedly at random intervals. Sometimes I get
several of these dialogs at once, sometimes just one.
>>
>> I know what an invalid certificate chain is, just not what to do
about it for this. Seems like the server is presenting the invalid
chain, which I can't really fix anyway, eh?
>>
>> Ideas?
>>
>> Windows 7, fully patched; Help/About says:
>> Pidgin 2.12.0 (libpurple 2.12.0)
>> Unknown
>>
>> (what's the "Unknown" about??)
>> And I'm using the Hangouts plugin.
>
>
_______________________________________________
[email protected] <mailto:[email protected]> mailing list
Want to unsubscribe? Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support
<https://pidgin.im/cgi-bin/mailman/listinfo/support>
_______________________________________________
[email protected] mailing list
Want to unsubscribe? Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support
_______________________________________________
[email protected] mailing list
Want to unsubscribe? Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support
