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

Implement ARI #284

Closed
mholt opened this issue Apr 25, 2024 · 2 comments · Fixed by #286
Closed

Implement ARI #284

mholt opened this issue Apr 25, 2024 · 2 comments · Fixed by #286
Assignees
Labels
feature request Request for new feature or functionality

Comments

@mholt
Copy link
Member

mholt commented Apr 25, 2024

The ACME Renewal Information (ARI) spec might be starting to stabilize, and Let's Encrypt just announced that renewals complying with ARI will not be rate limited. That was my primary concern, was intentionally refusing service to clients especially during times of infrastructure strain when reliability is already questionable and the renewal window is narrowing.

This sets a good precedent going forward and hopefully other CAs who implement ARI will follow their example.

I still have multiple reservations regarding the philosophy behind ARI, but I think it's probably worth implementing, at least with some configuration, since the policies behind ARI can still vary between CAs. For example, a CA might offer ARI, but in a way that does not actually help you ensure reliability when you comply with it. CertMagic's implementation will balance site uptime with optional protocols.

Let's Encrypt has an article to guide the implementation of ARI. ACMEz, CertMagic's underlying ACME library, already supports the latest ARI draft, but CertMagic will need to keep track of state and do some polling and scheduling to make ARI happen for the user.

@mholt mholt added the feature request Request for new feature or functionality label Apr 25, 2024
@mholt mholt self-assigned this Apr 25, 2024
@oliverpool
Copy link
Contributor

Tailscale Takeaways could be interesting to look at (BSD-3 license).

@mholt
Copy link
Member Author

mholt commented May 4, 2024

This is being staged at #286

@mholt mholt linked a pull request May 4, 2024 that will close this issue
3 tasks
@mholt mholt closed this as completed in #286 May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Request for new feature or functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants