(no title)
IgorPartola | 11 days ago
I suppose the same is true for DNS-01 but this would make it even easier because the attacker can just put up their LE account instead of mine into the DNS response and get a certificate.
At this point why not just put my public cert into a DNS record and be done with it?
gurjeet|11 days ago
If someone can perform MITM attack between LetsEncrypt and a DNS server, we've got bigger problem than just certificate issuance.
pests|10 days ago
They have a good reputation, lock down the domain technically at all levels, and have the connections and people/social skills to take care of any domain issues involving person-to-person contact.
Which is not easy, I recall spending months like a decade ago on email/phone attempting (successfully) to get my personal domain out of expiry hell (made more complicated by wrong records).
bombcar|11 days ago
Try to figure out a way to block me from getting a TLS certificate if I can modify your DNS.
IgorPartola|11 days ago
echoangle|11 days ago
msmith|11 days ago
Let's Encrypt has been doing this for several years, and it's a requirement for all CAs as of 2024.
[1] https://cabforum.org/2024/08/05/ballot-sc067v3-require-domai...
tkel|11 days ago
https://www.sidn.nl/en/modern-internet-standards/e-mail-secu...