3 ms·
I agree but I think registration and configuration should be split a little bit more. I personally won't trust it with my config files (and god knows what other
by toyg 11y ago
I agree but I think registration and configuration should be split a little bit more. I personally won't trust it with my config files (and god knows what other wonderful webserver will emerge next month), but having an automated cert-generation tool is great.
Also, they absolutely must improve OSX support. One of the main objectives is to help people who are in the web field but wouldn't otherwise bother learning the intricacies of SSL configuration; these people by and large use Macs.
- Natanael_L 11y agoThere's alternative tools that use the same standard API, you don't need to use the standard tool. If you want it to only register and authenticate to fetch a cert but not install it, and you want it to just tell you what you need to do so that you can do it manually if you so wish, then that's possible.
- tokenizerrr 11y ago> I agree but I think registration and configuration should be split a little bit more. I personally won't trust it with my config files (and god knows what other wonderful webserver will emerge next month), but having an automated cert-generation tool is great. The official client can be ran in 'auth' mode, in which it will not write to your server configs. It can still automate the authentication process for you by looking at where the DocumentRoot is, and placing a file there. But this is also optional, since there is a manual authentication mode as well that just gives you a file, and you'll have to make it available under your domain somewhere and tell it when you've done so. > Also, they absolutely must improve OSX support. One of the main objectives is to help people who are in the web field but wouldn't otherwise bother learning the intricacies of SSL configuration; these people by and large use Macs. They also use Mac on their servers?
- toyg 11y ago> The official client can be ran in 'auth' mode I know, I just think "auth mode" could be a separate tool to improve usability. It might just be an alias, I don't care, but it's easier to remember "get-cert" than yet another double-dash parameter IMHO. > They also use Mac on their servers? No, but very often they develop and try new tools on their Macs. By blowing the mac experience you're forcing them/us to spin up a vm (if you can) and repeat the installation. This raises the bar for adoption a little bit. In these fickle times, it can make the difference between "oh wow this is magic" and "can't be arsed, will check it out later/never".
- tokenizerrr 11y ago> I know, I just think "auth mode" could be a separate tool to improve usability. It might just be an alias, I don't care, but it's easier to remember "get-cert" than yet another double-dash parameter IMHO. It's a subcommand, not a "double-dash parameter". You have to supply one of the following, for it to do anything: (default) run Obtain & install a cert in your current webserver auth Authenticate & obtain cert, but do not install it install Install a previously obtained cert in a server revoke Revoke a previously obtained certificate rollback Rollback server configuration changes made during install config_changes Show changes made to server config during installation > No, but very often they develop and try new tools on their Macs. By blowing the mac experience you're forcing them/us to spin up a vm (if you can) and repeat the installation. This raises the bar for adoption a little bit. In these fickle times, it can make the difference between "oh wow this is magic" and "can't be arsed, will check it out later/never". It's a tool meant for servers, to configure server software. I'm not sure why anyone would want to run it on their development machine, especially since a domain name needs to be pointed towards a webserver running on that machine that is accessible from the WAN.
- toyg 11y ago>It's a subcommand, not a "double-dash parameter" Huge difference... Not. > I'm not sure why anyone would want to run it on their development machine Do you usually download and run random tools for the first time directly on a server box? > a webserver running on that machine that is accessible from the WAN Ok then you really should specify this somewhere. I've gone through the github readme and the User Guide without this being mentioned anywhere. I'm probably stupid for not running arbitrary beta tools on random wan-facing servers, but I'm certainly not the only stupid person in IT today.
- tokenizerrr 11y ago> Huge difference... Not. It's required to supply a subcommand, or it won't do anything. That is a big difference from a flag which you may forget to use, and then the program runs anyway. > Do you usually download and run random tools for the first time directly on a server box? I usually spin up a virtual machine for testing out server stuff. > Ok then you really should specify this somewhere. I've gone through the github readme and the User Guide without this being mentioned anywhere. I'm probably stupid for not running arbitrary beta tools on random wan-facing servers, but I'm certainly not the only stupid person in IT today. Me? I'm just a happy let's encrypt beta user. https://letsencrypt.org/howitworks/technology/ https://letsencrypt.org/howitworks/technology/ seems like a pretty clear, easy to comprehend, overview to me. I'm not sure how you were planning on validating ownership of a domain to a third party if you don't want that third party to request resources served by that domain.