3 ms·
”The client should decide whether the certificate is still trustworthy” That’s what is happening now. Except for common sense, nothing stops a browser from tru
by Someone 7y ago
”The client should decide whether the certificate is still trustworthy”
That’s what is happening now. Except for common sense, nothing stops a browser from trusting a certificate with an expiration date in the past.
The expiration date more is a statement from the issuer “I wouldn’t trust this after this timestamp”.
Having said that, I think Apple should say “our OSes will stop trusting certificates issued over two years ago” instead of ”our OSes will stop trusting certificates that expire in over two years”
If they did that, one could still use certificates with longer expiration periods, allowing other parties to cache them for longer periods.
Now they force everybody to follow them, so that, if this change breaks sites on iOS, it also breaks sites everywhere else.
- richardwhiuk 7y agoEveryone would just issue certificates for two years longer. This is designed to fix the fact that revocation is utterly broken.