HN user

jdkasten

5 karma

https://jdkasten.com PhD Candidate, University of Michigan Currently working on Let's Encrypt

[ my public key: https://keybase.io/jdkasten; my proof: https://keybase.io/jdkasten/sigs/uglZQNU2zUjedfafBipOUwrRts2fV0mPglRTwUP9XMo ]

Posts0
Comments3
View on HN
No posts found.

Yes, there are now several options to manually attain the certificate.

There is a "manual" mode, "Here is the file that you need to post, press Enter when you are ready to continue"

There is a "standalone" option. If you don't have a webserver running, it will bind to port 443 and solve the challenge for you.

There is also a "Webroot" option. Enter in your server's webroot and it will automatically post a file to .well-known and delete the file after validation.

That will be an option.

Also, the current implementation only changes the SSLCertificateFile directive if you provide your own --key, --csr and already have an SSL vhost for the domain. (This one change is logged.)