3 ms·
They could even do something really crazy like telling everybody about the change in advance so third-party developers could double-check their code and make su
by mikeash 11y ago
They could even do something really crazy like telling everybody about the change in advance so third-party developers could double-check their code and make sure it still worked.
- blinkingled 11y agoYes! Communication is the first measure to try before anything technical as a second line of defense - but that's not a part of Apple's DNA :)
- rdancer 11y agoThe expiration date is part of the certificate description. Events like this happen day-in, day-out. "Telling everybody" is not the solution, comprehensive testing is.
- mikeash 11y agoThe problem wasn't simply the expiration date, but also issuing new certificates with SHA-256 instead of SHA-1. That's a big change you ought to tell developers about when it's their software that had to deal with those certificates.