3 ms·
> but the key problem is dealing with older operating systems that either don't have the correct root certificate, or don't have support for either the SHA-1 or
by bawolff 6y ago
> but the key problem is dealing with older operating systems that either don't have the correct root certificate, or don't have support for either the SHA-1 or ECDSA protocols that are used in the process of verifying a certificate.
Say what now? Pretty sure sha-1 support for certs is much older than android 7.
- tialaramex 6y agoThe article has quite a few mistakes. Nobody issues with SHA-1 any more, haven't for several years. It's almost all SHA-256 and at Let's Encrypt I believe it always has been because SHA-1 deprecation was already well underway before they span up Let's Encrypt so it would have made no sense to implement that only to immediately rip it back out.
- schoen 6y ago> at Let's Encrypt I believe it always has been True! https://crt.sh/?id=9314793 https://crt.sh/?id=9314793
- tialaramex 6y agoThis is the (first) helloworld.letsencrypt.org test certificate. Now, for most (perhaps even all other?) Certificate Authorities that doesn't prove much, because after all you could manually cause issuance of anything. But the fun thing about Let's Encrypt is they've insisted almost to a fault upon only using their ACME API. After all, if you really believe in everybody else using automation it's hypocritical to have manual systems for your own stuff. [ I say almost to a fault because there can be situations where for compliance you need to demonstrate something and it seemed (I may be wrong and Seth will correct me) as though Let's Encrypt always chose to just let nature take its course instead. Want to see an expired certificate? We'll put one of our auto-generated certificates on a server, and then just wait ninety days for it to expire. ] So as a result helloworld.letsencrypt.org isn't just a proof that they could issue such certificates, it means logically that's what all the certificates looked like at that time.
- schoen 6y agoI wasn't close enough to the process to be certain of this, but I believe you're totally correct here. At least I know that there is no UI for manual issuance (or for manually resetting a rate limit condition), so there's no person you can call up and try to harangue/social engineer into doing these things for you.
- GordonS 6y agoI guess they meant SHA-256?
- alblue 6y agoYeah, my mistake - have fixed. Thanks for the feedback!