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.

Sign up for GitHub

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

Jump to bottom

Reach out to ACME client implementations to recommend ECDSA #254

Open
april opened this issue Jun 20, 2019 · 1 comment
Open

Reach out to ACME client implementations to recommend ECDSA #254

april opened this issue Jun 20, 2019 · 1 comment

Comments

@april
Copy link
Contributor

april commented Jun 20, 2019 •
edited

I'm not sure how much time I'll have to do this, but I wanted to create an ongoing thread to encourage independent ACME implementations to switch to ECDSA as part of the upcoming Server Side TLS 5.0 updates:

#178
https://letsencrypt.org/docs/client-options/

ACME v2

Certbot: certbot/certbot#6492
acme.sh: acmesh-official/acme.sh#2350
dehydrated: dehydrated-io/dehydrated#651
GetSSL: srvrco/getssl#417
cPanel: Emailed @bennyvasquez

Go

Caddy: caddyserver/caddy#2650 (ecdsa256 by default)
Lego: Already uses ecdsa384 by default

Java

Acme4j: shred/acme4j#78 (documentation updated)
@april april changed the title Reach out to ACME client implements to recommend ECDSA Reach out to ACME client implementations to recommend ECDSA Jun 20, 2019
This was referenced Jun 20, 2019
Open
Closed
Closed
Closed
@ghen2
Copy link

ghen2 commented Nov 30, 2022

Certbot 2.0 and (soon) acme.sh have made the switch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@april @ghen2