The certificate is not trusted because no certificate that can verify it is currently trusted.
I also frequently see this in relation to modem resets & changing wireless hosts while travelling (esp.
with locations that force redirect to accept TOS for their wifi). I agree that it's the desired behavior, as I don't need anyone impersonating me (which is why you DO care about this smitty), but perhaps we can figure out what is causing it anyways?
its just a certificate that popsup, but it needs to be handle by pdgin instead of waiting for user input.
So yes the user has to accept it, otherwise pidgin doesnt get back online. just curious but could it be a "feature" of my 2-Wire (brand) modem ?
maybe their various login servers have different certs? My last screenshot indicates that the cert is valid starting in feb? This appears to be a similar ticket - https://api.net/auth/client Login ', I do see the correct AOL delivered error message.
(I do not have an ICQ account mind you.) Also, I have no machine local firewall, or anything beyond standard NAT'ing in my router. I cannot think of anything else to add, except that maybe the dialog should be integrated into the buddylist, where the subsequent SSL error is in my first sshot?
The certificate claims to be from "gateway.2wire.net" instead.
This could mean that you are not connecting to the service you believe you are.
perso, i see it as 2 things, my modem bothering to send an error back to my computer and pidgin not handling this error message like it should.