update letsencrypt v2 compatible clients list at https://letsencrypt.org/docs/client-options/ to indicate that greenlock-cli is compatible with ACME v2 #3

New Issue

Ghost · 2019-11-14T21:04:37Z

Ghost commented

2019-11-14 21:04:37 +00:00

Looks like a great project. If greenlock-cli does support ACME v2 (which I believe is the case from what I have heard and read), then I suggest you submit PR to update https://letsencrypt.org/docs/client-options/ since their documentation page of compatible clients doesn't indicate that you support v2 otherwise people might get the wrong impression. Clients marked with an asterisk (*) are thought to only be v1 clients. The repo with the source for this website is at: https://github.com/letsencrypt/website/

You might also want to include the root greenlock project besides cli and express versions.

On that page it indicates that this would accomplished by a pull request:

If you know of an ACME client or a project that has integrated with Let’s Encrypt that is not present in the above page please submit a pull request to our website repository on Github, updating the data/clients.json file.

Before submitting a pull request please make sure:

Your client respects the Let’s Encrypt trademark policy.

Your client is not browser-based and supports automatic renewals.

Your commit adds your client to the end of the relevant sections (Don’t forget the “acme_v2” if appropriate!).

Your commit updates the lastmod date stamp at the top of clients.json.

Looks like a great project. If greenlock-cli does support ACME v2 (which I believe is the case from what I have heard and read), then I suggest you submit PR to update https://letsencrypt.org/docs/client-options/ since their documentation page of compatible clients doesn't indicate that you support v2 otherwise people might get the wrong impression. Clients marked with an asterisk (*) are thought to only be v1 clients. The repo with the source for this website is at: https://github.com/letsencrypt/website/ You might also want to include the root greenlock project besides cli and express versions. On that page it indicates that this would accomplished by a pull request: > If you know of an ACME client or a project that has integrated with Let’s Encrypt that is not present in the above page please submit a pull request to our website repository on Github, updating the data/clients.json file. > Before submitting a pull request please make sure: > - Your client respects the Let’s Encrypt trademark policy. > - Your client is not browser-based and supports automatic renewals. > - Your commit adds your client to the end of the relevant sections (Don’t forget the “acme_v2” if appropriate!). > - Your commit updates the lastmod date stamp at the top of clients.json.

Ghost changed title from ~~update letsencrypt v2 compatible clients at https://letsencrypt.org/docs/client-options/ to indicate that greenlock is compatible with ACME v2~~ to update letsencrypt v2 compatible clients at https://letsencrypt.org/docs/client-options/ to indicate that greenlock-cli is compatible with ACME v2

2019-11-14 21:04:59 +00:00

Ghost changed title from ~~update letsencrypt v2 compatible clients at https://letsencrypt.org/docs/client-options/ to indicate that greenlock-cli is compatible with ACME v2~~ to update letsencrypt v2 compatible clients list at https://letsencrypt.org/docs/client-options/ to indicate that greenlock-cli is compatible with ACME v2

2019-11-14 21:06:12 +00:00

Sign in to join this conversation.

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coolaj86/greenlock-cli.js#3