3 ms·
In effect that is sort of what they are doing, but simpler. You claim to have domain x.com. LetsEncrypt sends you a token. Place it in a DNS record or in a pre
by breakingcups 9y ago
In effect that is sort of what they are doing, but simpler.
You claim to have domain x.com. LetsEncrypt sends you a token. Place it in a DNS record or in a pre-determined path on your domain and ask LetsEncrypt to read it back.
If it matches, it is verified that you own the domain.
How is the scheme you propose simpler, whilst retaining the same base guarantee (that the requester is the owner of the domain in question)?
- TekMol 9y ago> in a pre-determined path on your domain That would be easy and elegant. But they want you to install software on your server.
- icebraining 9y agoThey want to make it easier, and that's the easiest way, but it's not required. You can perfectly well run it on your machine and copy the files manually to the server. You can even use a simple webpage as your local client: https://gethttpsforfree.com/ https://gethttpsforfree.com/
- corford 9y agoThe only software you need is something that can speak the ACME protocol, which is what letsencrypt uses to receive your CSR (which you can generate yourself with openssl), issue challenge tokens and then (subject to you successfully passing the challenge) give you a certificate. You don't necessarily have to do any of the above on the server for which you want the certificate. You can do it somewhere else and then transfer the resulting certificate to the intended host (either manually or with a shell script/ansible/puppet whatever).
- louiz 9y agoThe software just negociates the token and such things, and communicates with EL to say “I want to have a certificate for such and such domains”. But you can place these tokens on your webserver by hand if you want, in a pre-determined path.