Skip to content
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

Comprehensive support for ACMEv2 (tracking issue) #5365

Closed
ohemorange opened this issue Jan 4, 2018 · 3 comments
Closed

Comprehensive support for ACMEv2 (tracking issue) #5365

ohemorange opened this issue Jan 4, 2018 · 3 comments
Assignees
Milestone

Comments

@ohemorange
Copy link
Contributor

ohemorange commented Jan 4, 2018

  1. Get ACMEv2 support in acme module
  2. Get ACMEv2 support in Certbot
  3. Get DNS plugins installable
  4. Change the default ACME server to the v2 endpoint
@cpu
Copy link
Contributor

cpu commented Jan 5, 2018

@ohemorange Does Certbot support TLS-SNI-02 challenges? If not I think that will require one more sub-issue. The V2 API is offering TLS-SNI-01 right now but it will be removed shortly and replaced with TLS-SNI-02.

Edit: TLS-SNI-01/02 are no longer supported and SNI-02 support doesn't make sense anymore.

@ohemorange
Copy link
Contributor Author

@cpu not yet, thanks for the reminder!

@bmw
Copy link
Member

bmw commented Mar 1, 2018

We have some str/bytes issues in Python 3 which should be fixed by #5606, but otherwise, this issue has been resolved.

@bmw bmw closed this as completed Mar 1, 2018
dnet added a commit to dnet/website that referenced this issue Mar 14, 2018
cpu pushed a commit to letsencrypt/website that referenced this issue Mar 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants
@cpu @ohemorange @bmw and others