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

ECDSA account keys #2209

Closed
kuba opened this issue Jan 16, 2016 · 6 comments
Closed

ECDSA account keys #2209

kuba opened this issue Jan 16, 2016 · 6 comments
Labels
area: acme feature request priority: significant Issues with higher than average priority that do not need to be in the current milestone.

Comments

@kuba
Copy link
Contributor

kuba commented Jan 16, 2016

Similar to #2163, however there might be no support on the Boulder side at all yet.

@alex
Copy link
Collaborator

alex commented Jan 16, 2016

Boulder support was landed in letsencrypt/boulder#1357

@kuba
Copy link
Contributor Author

kuba commented Jan 16, 2016

Oh, thanks once again, @alex!

@pfigel
Copy link
Contributor

pfigel commented Sep 2, 2016

Related to this, it looks like it's currently not possible to revoke EC certificates using the certificate key. If I'm reading the stack trace correctly (see link below), this might be due to the request signing code only expecting (or supporting) RSA keys, so I'm guessing a fix for this issue would also solve the revocation issue. LMK if I'm missing something and this is a separate issue.

Further details: https://community.letsencrypt.org/t/cant-revoke-ec-certs-error-but-rsa-cert-revokes-ok/18820

@pde pde added this to the 1.0.0 milestone Dec 8, 2016
@pde pde added the has pr label Dec 8, 2016
@ageis
Copy link

ageis commented Aug 27, 2017

Wrote a related comment and I support this unreservedly. Are you having a hackathon anytime soon? I'd probably ease into development better that way, with a single day of hand-holding, but feel free to point me to low-hanging fruit issues for now.

@stale
Copy link

stale bot commented Jun 11, 2019

We've made a lot of changes to Certbot since this issue was opened. If you still have this issue with an up-to-date version of Certbot, can you please add a comment letting us know? This helps us to better see what issues are still affecting our users. If there is no further activity, this issue will be automatically closed.

@stale stale bot added needs-update and removed needs-update labels Jun 11, 2019
@certbot certbot deleted a comment from lnicola Jun 11, 2019
@bmw bmw added the priority: significant Issues with higher than average priority that do not need to be in the current milestone. label Mar 20, 2020
@bmw bmw removed this from the Important milestone Mar 20, 2020
atombrella added a commit to atombrella/certbot that referenced this issue Aug 28, 2020
This solves certbot#2209, certbot#2625 and certbot#3349

Co-Authored-By: Tomoyuki-GH <55397638+Tomoyuki-GH@users.noreply.github.com>
@bmw bmw removed the has pr label Oct 6, 2020
@atombrella
Copy link
Contributor

I think this depends on finishing this class https://github.com/certbot/josepy/blob/master/src/josepy/jwk.py#L124

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: acme feature request priority: significant Issues with higher than average priority that do not need to be in the current milestone.
Projects
None yet
Development

No branches or pull requests

8 participants