Sky, the cert fails because I'm (very, very slowly) trying out
different PGP-SSL bridges (it's four or five projects down, at this
point). Right now, this means that my cert is self-signed, and that
it can be verified by checking the PGP signature on the authentication
statement:
http://lists.ali
Rapidly means several days to a week for google.com. We (Cyberspark.net) watch
the Google.com SSL certs (not gmail) and it takes at least a few days as they
roll new certs onto multiple IP addresses (round robin DNS). I have only
monitored this for the last two years, but it's been the same both
John Adams writes:
> On Sat, Jan 12, 2013 at 2:54 PM, John Adams wrote:
>
>> Google has stated publically that they rapidly roll their SSL
>> certificates. Nothing to see here, no blog post to write, move along
>> now...
Thanks for pointing that out, I must've missed those announcements.
> Add
Additionally, while you're complaining about other people's SSL
certificates, you should fix yours. :)
[image: Inline image 1]
On Sat, Jan 12, 2013 at 2:54 PM, John Adams wrote:
> Google has stated publically that they rapidly roll their SSL
> certificates. Nothing to see here, no blog post to
Google has stated publically that they rapidly roll their SSL certificates.
Nothing to see here, no blog post to write, move along now...
-j
On Sat, Jan 12, 2013 at 2:19 PM, Nick M. Daly wrote:
> Hi folks, can you help me understand how to interpret this data? It
> appears that Gmail's SSL ce
Hi folks, can you help me understand how to interpret this data? It
appears that Gmail's SSL certificate changed fairly frequently during
the month of December. That seems wrong to me. What's this all mean?
https://www.betweennowhere.net/blog/2013/01/gmails-changing-ssl-certificates/
The weird
