5 ms·

Also see https://godoc.org/golang.org/x/crypto/acme https://godoc.org/golang.org/x/crypto/acme and https://github.com/xenolf/lego https://github.com/xenolf/leg

Also see https://godoc.org/golang.org/x/crypto/acme https://godoc.org/golang.org/x/crypto/acme and https://github.com/xenolf/lego https://github.com/xenolf/lego Go has some of the best letsencrypt tooling out there, and there was even some support for merging ACME support directly into net/http https://github.com/golang/go/issues/17053 https://github.com/golang/go/issues/17053

mikecb 10y ago
I just recently used lego for dns based issuance, and it was excellent.
- newman314 10y ago
  +1 on lego. I'm a happy user.
- petre 10y ago
  True. I've tried 3 or 4 clients in Perl, Node.js. Only lego worked flawlessly. And the Caddy HTTP/2 webserver also has excellent ACME support.
zuzun 10y ago
The developers working on the crypto/acme extension also wrote a stand-alone client: https://www.github.com/google/acme https://www.github.com/google/acme. Very easy to use, can only recommend it!
- eternalban 10y ago
  rsc's code is using /acme from https://github.com/xenolf/lego https://github.com/xenolf/lego (same thing?)
eriknstr 10y ago
I've been hosting my website using the https://github.com/diafygi/acme-tiny https://github.com/diafygi/acme-tiny Python script running along with Nginx on a Raspberry Pi 1 Model B with reverse-proxy caching provided by CloudFlare from my home line for several months now. I have repo where I detail the setup and provide some config files and scripts. I've been thinking about posting about it to HN but have not submitted it because (a) Some of it might still be incomplete. Even though my website works perfectly, I don't remember if I've recorded absolutely everything that is needed or not. (b) I have written a script to obtain the WAN IP from our router rather than using a 3rd party service. This is great for me because it means one less thing to worry about, but it also means that for others who are using different routers, their setup will require adjustments. (c) Getting any attention on HN is hard. Submitted posts are most likely to gain a few couple upvotes before they quickly drown in the masses. Anyway, since we were on the subject of other tools to use for Let's Encrypt, I figured I'd bring up acme-tiny, and when I had done so, I might as well mention all of the rest I said above. Here's my write-up and related files: https://github.com/eriknstr/interweb https://github.com/eriknstr/interweb

mikecb 10y ago

I just recently used lego for dns based issuance, and it was excellent.

newman314 10y ago
+1 on lego. I'm a happy user.
petre 10y ago
True. I've tried 3 or 4 clients in Perl, Node.js. Only lego worked flawlessly. And the Caddy HTTP/2 webserver also has excellent ACME support.

zuzun 10y ago

The developers working on the crypto/acme extension also wrote a stand-alone client: https://www.github.com/google/acme https://www.github.com/google/acme. Very easy to use, can only recommend it!

eternalban 10y ago
rsc's code is using /acme from https://github.com/xenolf/lego https://github.com/xenolf/lego (same thing?)

eriknstr 10y ago

I've been hosting my website using the https://github.com/diafygi/acme-tiny https://github.com/diafygi/acme-tiny Python script running along with Nginx on a Raspberry Pi 1 Model B with reverse-proxy caching provided by CloudFlare from my home line for several months now. I have repo where I detail the setup and provide some config files and scripts. I've been thinking about posting about it to HN but have not submitted it because (a) Some of it might still be incomplete. Even though my website works perfectly, I don't remember if I've recorded absolutely everything that is needed or not. (b) I have written a script to obtain the WAN IP from our router rather than using a 3rd party service. This is great for me because it means one less thing to worry about, but it also means that for others who are using different routers, their setup will require adjustments. (c) Getting any attention on HN is hard. Submitted posts are most likely to gain a few couple upvotes before they quickly drown in the masses. Anyway, since we were on the subject of other tools to use for Let's Encrypt, I figured I'd bring up acme-tiny, and when I had done so, I might as well mention all of the rest I said above. Here's my write-up and related files: https://github.com/eriknstr/interweb https://github.com/eriknstr/interweb