Let's Encrypt: How It Works
How is this not really bad?<p>Suppose I somehow get control of a machine on the same network as a server that doesn't use Let's Encrypt.  I can probably ARP spoof it pretty easily.  If it has a signed certificate from a different CA, I can't MITM it without people noticing.  Or I couldn't, until now!  Because I can now "control" the server's responses, I can easily get Let's Encrypt to authorize a new key pair giving my control over that domain.  I can now generate valid certs for my MITM keys.<p>If the server were already using Let's Encrypt, I couldn't create a new controlling key pair.  The "How It Works" doesn't talk about that, but search the RFC for "recovery token".  But if the server isn't using Let's Encrypt, what would stop me from doing this?<p>Of course, I'm actually on the other end of it.  To project myself, do I really have to at least register a controlling key pair with Let's Encrypt and any other browser-supported CAs that adopt this protocol?