2 ms·
Yeah that's likely the issue. Actually, looking at all the root CA certs on my computer (OS X, look in Keychain.app if you're curious) every single one of them
by tlrobinson 18y ago
Yeah that's likely the issue. Actually, looking at all the root CA certs on my computer (OS X, look in Keychain.app if you're curious) every single one of them (except one) expires in 2037 or earlier.
This is almost certainly not a coincidence. In software that doesn't take the Y2K38 issue into account the expiration date would wrap around to an earlier date, causing the software to think the cert is invalid.
- jwilliams 18y agoAh ok - yeah, I've hit that issue in testing before. I'd be surprised if 2038 was the reason though - most certificates are very conservative about expiry. You'd never have a cert that lasts to 2038 as there is a high probability that the cert would be cracked well before that date (i.e. even if it's brute-force, likely computers in "n" years time will be able to crack it).
- tlrobinson 18y agoI would have thought that too, except there's a bunch of certs with expirations all the way up to 2037 at which point they abruptly stop (except for the one 2040)... http://tlrobinson.net/skitches/Keychain_Access-20090106-000936.png http://tlrobinson.net/skitches/Keychain_Access-20090106-0009...