Re:Let's Encrypt: How It Works
by bifurcation on Friday November 21, 2014 @07:06PM
(#8644120)
Yes, we plan to apply a few mitigations of this type. Part of the idea of the "Proof of Possession of a Prior Key" challenge is so that if a web server requests a cert for a domain with an existing certificate, we can ask them to prove that they hold that certificate.
https://github.com/letsencrypt/acme-spec/blob/master/draft-b...
Re:Let's Encrypt: How It Works
by angry_octet on Saturday November 22, 2014 @04:16AM
(#8645177)
Also, it seems possible that large scale DOS could be performed by applying for domains (via DNS hijack) before the owners do, causing significant administrative burden to recover from. I would suggest allowing simpler revocations within some multiple of the DNS TTL value for the domain.
I can also envision unscrupulous registrars pre-applying for LE certs for a fee, like $5.99 per month, and being very tardy and uncooperative about relinquishing control.
Re:Let's Encrypt: How It Works
by iancarroll on Friday November 21, 2014 @09:57PM
(#8644546)
This is a horrible idea... I have numerous certs for my domain and collecting them all to prove to you I own them is not going to be fun.
Re:Let's Encrypt: How It Works
by angry_octet on Saturday November 22, 2014 @04:18AM
(#8645180)
You wouldn't be in a very good position to revoke them then, would you? For example, if we had another heartbleed.
Re:Let's Encrypt: How It Works
by iancarroll on Saturday November 22, 2014 @10:45AM
(#8645753)
I have access to manage them, however the private keys are either in various services or non exportable with AWS...
Doing this would prevent a point in time vulnerability in DNS (temporary mitm showing a different IP for the domain) or direct mitm of the connection to the webserver. Otherwise the attacker could get a signed cert for https://peacenik.org, and then present that to activists that it mitms.