3 ms·
Logs are there because any person at any CA can generate a cert for your domain and we want to know when that happens. We should fix that. A new standard could
by throwaway787544 4y ago
Logs are there because any person at any CA can generate a cert for your domain and we want to know when that happens. We should fix that.
A new standard could dictate that registrars and CAs have to work together. Specifically, customer uploads a public key to a registrar, and a CA has to use registrar's public key to validate a CSR. This makes it impossible to create a valid certificate without the domain owner's key - and not whoever took over the domain record for the moment that the CA validated. The browser should validate that the cert was signed using the key from the registrar.
In this way even a rogue CA cert can't work on a client. Only a cert created by the domain owner will be valid. So only one CA and one key can create a valid cert.
- Anunayj 4y agoAt that point, why even have CAs? Why not just use something like DANE [1]. [1] https://en.m.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities https://en.m.wikipedia.org/wiki/DNS-based_Authentication_of_...
- throwaway787544 4y agoBecause it requires DNSSEC, and the impact of misconfiguring DNSSEC is unnecessarily high just to validate a certificate. Something like DANE that didn't require DNSSEC would work great I think