Re:CA Comodo used broken OCR and issued certificates to the ...
by tokenizerrr on Friday October 21, 2016 @02:45PM
(#12763366)
Yes, this is called domain validation and most CAs operate like this for regular non-EV certificates. Sometimes it's an email, sometimes it's a file with certain content at a certain URL, sometimes it's a DNS record. But beyond that, no further validation is required for regular certificates.
Re:CA Comodo used broken OCR and issued certificates to the ...
by AndyMcConachie on Friday October 21, 2016 @03:41PM
(#12763924)
I don't know why you were down voted. Yes, Let's Encrypt does verification by requiring a site to host a string on port 80. They discover the site via DNS, and they do NOT require DNSSEC. Thus you can absolutely trick Let's Encrypt into issuing a bad cert if you can serve them bad DNS responses.
This OCR issue with Comodo in TFA concerns WHOIS data, which may or may not be more reliable than unsigned DNS data. Regardless your point remains valid.
Re:CA Comodo used broken OCR and issued certificates to the ...
by tokenizerrr on Friday October 21, 2016 @04:10PM
(#12764202)
You can also trick practically every other CA using the same techniques.
Re:CA Comodo used broken OCR and issued certificates to the ...
by AndyMcConachie on Friday October 21, 2016 @05:04PM
(#12764796)
Yes. And remember you only have to trick one of them for them all to be useless :)
It's good to encrypt things, but I wouldn't be too surprised if it were possible for folks to issue bad certs via them, as well.