3 ms·
They're generating the certificate, not the keys. Those are different things. You can probably think of the certificate as the computer equivalent of photo ID
by adamtj 12y ago
They're generating the certificate, not the keys. Those are different things. You can probably think of the certificate as the computer equivalent of photo ID for the server.
They both show who you are (Driver's License: your name, cert: hostname), what you look like (DL: photo of you, cert: the key's fingerprint) and provide proof that they are genuine (DL: difficult and illegal fake, cert: practically impossible to do the math to forge a signature).
Note that they mention certificate singing requests. If the CA generated the keys, it wouldn't also need a CSR. It could just generate and send you the public and private keys and the signed certificate for them. However, it does need some information about the keys it's signing. You provide that information in the form of a CSR.
- grey-area 12y agoLooks to me like it generates the keys locally OR you can specify the keys if you like. But since the private key doesn't leave your server, it doesn't really matter either way. https://github.com/letsencrypt/lets-encrypt-preview/blob/master/letsencrypt/client/client.py https://github.com/letsencrypt/lets-encrypt-preview/blob/mas...
- ecoffey 12y agoThe driver license analogy is pretty great, I'll be stealing that :-)