-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with ACME v2 #101
Comments
Support for acme v2 is planned, but (unfortunately) not wildcard certificates support:
as Adding |
Yeah, For v2 support, we'll end up waiting until python-acme implements it, and from there I expect plumbing that through to simp_le won't be a ton of work. |
give us DNS-01, guys! stop being lazy... community and enterprise gave us a chance to have SSL certs for free and now you, guys, blocking it's usage for a full power! |
|
ACME v2 has been released and @zenhack Please note |
|
Yeah. We're unblocked on V2 support now that the library has implemented it, but it hasn't happened just yet. |
Yes, I misread the hierarchy of headlines.
…On 13 March 2018 at 19:51, Ian Denhardt ***@***.***> wrote:
Yeah. We're unblocked on V2 support now that the library has implemented
it, but it hasn't happened just yet.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#101 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABka_BrQYQMSgL4xKMCPXW1WQrSgGiGHks5teBUfgaJpZM4RWq27>
.
|
Yep, good call -- closing. |
* GetCert client is deprecated in favor of GetCert2 * simp_le supports acmev2 per zenhack/simp_le#101 * Greenlock for nodejs supports acmev2 * Certificaat supports acmev2
* GetCert client is deprecated in favor of GetCert2 * simp_le supports acmev2 per zenhack/simp_le#101 * Greenlock for nodejs supports acmev2 * Certificaat supports acmev2
Great work @zenhack, I was wondering if you have any plans to support the upcoming ACME v2 endpoint:
https://community.letsencrypt.org/t/staging-endpoint-for-acme-v2/49605
It was announced a few days ago and highlights among others include support for wildcard certs! The staging environment is already live with a full launch date scheduled for February 27th 2018.
The text was updated successfully, but these errors were encountered: