Re:StartSSL domain validation vulnerability
by pfg on Monday March 21, 2016 @05:25PM
(#11332217)
It's certainly easier for automation. I think the security implications are mostly the same - you're vulnerable to DNS spoofing and BGP hijacking either way. With email validation, a misconfigured or breached email server is enough to get a certificate, while with http validation, it's your web server or web app that could be vulnerable.
[ Parent
| on HN ]
Re:StartSSL domain validation vulnerability
by brohee on Wednesday March 23, 2016 @11:45AM
(#11345477)
And a vulnerability in your website permitting an attacker to create a file opens the possibility for an attacker to get a certificate for your site too, and without certificate transparency you'll possibly never even know it even happened...