2 ms·
So, the way X.509 works, certificates aren't signed by a particular other certificate, but by a named Issuer and private key. This particular Issuer, "Google In
by tialaramex 10y ago
So, the way X.509 works, certificates aren't signed by a particular other certificate, but by a named Issuer and private key. This particular Issuer, "Google Internet Authority G2" has both an older SHA-1 certificate (which expires when you said) and a newer SHA-256 certificate, with the same key that expires a year later. So, there are two things that might happen here, one is their fault, one is (maybe) yours
1. They could be sending the SHA-1 intermediate instead of the correct SHA-256 intermediate. This would affect everyone connecting to that particular server. Google has to fix this by correcting the intermediate certificate delivered during TLS handshake.
2. Your client (browser) could have cached the SHA-1 certificate from somewhere and be relying on it (because the name and key match) even though Google provided a SHA-256 certificate that's better.
If you can still reproduce the error, tools like openssl's s_client mode can dump all the certificates sent over, and don't have a cache of their own, so that's useful for diagnosis.