6 ms·
Why? It seems to me like it should be really simple: I prove I control domain X, they issue me a certificate for domain X. End of story. Does there need to be m
by mikeash 12y ago
Why? It seems to me like it should be really simple: I prove I control domain X, they issue me a certificate for domain X. End of story. Does there need to be more?
- UnoriginalGuy 12y agoWhat if someone hijacks a domain? Should they issue one then? I'll say this, I don't want to see "Let's Encrypt" go on some moral crusade deciding not to grant a certificate to a website because that website contains offensive content, but their job is to verify at least somewhat the identity of the requester to try and stem impersonation.
- the8472 12y ago> What if someone hijacks a domain? But that's a registrar problem, not a "proof that this connection comes from someone who controls that domain" problem. These aren't EV certificates.
- tedunangst 12y agoThe fact that I seized a domain ten years ago doesn't mean I'm not who I say I am today. Also, seizure and hijacking aren't equivalent.
- nly 12y agoWhat if a domain expires but a certificate for the domain has been issued by the previous owner?
- mikeash 12y agoI would think a cert shouldn't be issued with an expiration date after that of the domain registration itself.
- kijin 12y agoThat would work with common gTLDs, but some ccTLDs have a very annoying policy where they only allow one-year renewals and the renewal doesn't show up in the whois until the last moment. Anyway, it's trivial to find out whether a domain was expired and re-registered. The date of initial registration in the whois will change, so you can just compare it with the value you saw when you first issued a certificate for that domain.