News for hackers. Stuff that matters.
Re:O2 outage due to expired Ericsson certificate by admax88q on Thursday December 06, 2018 @05:37PM (#18623133)
Expiry dates are in years, if a key is compromised, then an adversary has _years_ to exploit a MITM.

However we already mitigate this with revocation lists. But if we can revoke certificates why do we have expiration dates?

Seems to me expiration dates are rent seeking behaviour by certificate vendors.

Re:O2 outage due to expired Ericsson certificate by nemothekid on Thursday December 06, 2018 @05:51PM (#18623245)
This is a reason to shorten expiration times, not remove them (which companies like LetsEncrypt are doing)
Re:O2 outage due to expired Ericsson certificate by admax88q on Friday December 07, 2018 @03:32PM (#18631340)
Why. If revocation already works why bother with expiration?
Re:O2 outage due to expired Ericsson certificate by jstanley on Thursday December 06, 2018 @05:42PM (#18623183)
One good reason is that if you buy a domain name that somebody else has used in the past, they don't have an infinite valid SSL certificate for your domain.
Re:O2 outage due to expired Ericsson certificate by AltF4me on Thursday December 06, 2018 @05:51PM (#18623246)
Would it not be possible to expire the cert if the domain expires?
Re:O2 outage due to expired Ericsson certificate by wiml on Thursday December 06, 2018 @07:13PM (#18623893)
No, that would be "revocation". Expiration is relatively easy to implement because the expiration date is known in advance and so you can simply put the expiration date in the certificate when it is issued. Revocation is relatively difficult because you need to continually check some database for revocation information — that's where CRLs, OCSP, and the like come in. And there's a lot of complexity under that hood, which, once the dust settles, boils down to just issuing very-short-lived certificates under a different guise.
Re:O2 outage due to expired Ericsson certificate by toast0 on Thursday December 06, 2018 @06:25PM (#18623549)
No. The certificate's expiration is fixed at time of issuance. You could set the expiration of the certificate to the expiration date of the domain, but the domain could be transferred, cancelled, or revoked before the expiration.
Re:O2 outage due to expired Ericsson certificate by LinuxBender on Thursday December 06, 2018 @05:54PM (#18623275)
Just a few years ago, almost nothing checked the revocation lists. I revoked certs for some popular domains and was concerned about ssl caches and proxies... turns out, an owl heard it. An odd dog barked. No impact. Not even from the folks that embedded our certs onto their servers for legacy code reasons. Perhaps this has changed over the last couple of years.
Re:O2 outage due to expired Ericsson certificate by admax88q on Friday December 07, 2018 @03:34PM (#18631358)
Yep. But that's an implementation problem. Revocation is a critical security feature. Complaining that people didn't used to check it is like complaining that people didn't used to encrypt.

You're not secure if you don't check revocation.

Re:O2 outage due to expired Ericsson certificate by LinuxBender on Friday December 07, 2018 @03:48PM (#18631457)
I agree with this. For the record, I am not complaining. :-) I just like to share my experiences of how things worked verses how they were intended to work.