Let's Encrypt Announces New-Certificate-Every-6-Days Offering
2 years ago by misk to c/technology
Yes X.509 is broken. If you're a developer and not pinning certs, you're doing it wrong.
What part are you confused about, and are you a developer?
Edit: why was I downvoted for asking this?
I'm saying that if you're a developer of software that communicates between two nodes across the internet, you shouldn't rely on X.509 because the common root stores have historically been filled with compromised CAs, which would let someone with that CA decrypt and view the messages you send with TLS.
You should mint your own certs and pin their fingerprints so that your application will only send messages if the fingerprint of the cert on the other end matches your trusted cert.
@lemmy.world
go to feed...
@lemmy.world
go to feed...
When I look at the default list of trusted CAs in my browser, I get the feeling that certificate lifetimes isn't the biggest issue with server certificates.
save