example using openssl, curl, netcat about acme-spec

[schoen]

The node client and server are both now substantially unmaintained, as far as I know. The current active development efforts by Let's Encrypt project members are Boulder (the server, written in Go)

https://github.com/letsencrypt/boulder

and lets-encrypt (the client, written in Python)

https://github.com/letsencrypt/lets-encrypt-preview

Because of protocol changes, Boulder and the Python client currently don't interoperate, and the client development is proceeding with the (generally unmaintained) node-acme server. Hopefully that will switch over soon.

[schoen]

For the time being, the lets-encrypt-preview client should interoperate correctly with the node version (at least, we've gotten it to do so every day in testing and development purposes). If you encounter a bug there, you could file an issue in lets-encrypt-preview and we should be able to address it promptly, at least if it's not highly OS-dependent.

[bifurcation]

Given that ACME requires JWS signing of requests (for which I don't know of any good client-side tools), I don't think this is practical.

[coolaj86]

Maybe some diagrams then? Something like these: https://www.digitalocean.com/community/tutorials/an-introduction-to-oauth-2?

[soullivaneuh]

Have some bash examples with a basic and complete auth process would be a very great addition.