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

Let's Encrypt Ending Support for Notification Emails #1643

Open
r3m8 opened this issue Feb 10, 2025 · 0 comments
Open

Let's Encrypt Ending Support for Notification Emails #1643

r3m8 opened this issue Feb 10, 2025 · 0 comments

Comments

@r3m8
Copy link

r3m8 commented Feb 10, 2025

Let’s Encrypt will discontinue support for expiration notification emails starting June 4, 2025. The email field processed by the ACME server will no longer be supported, including for technical information about the Let’s Encrypt infrastructure. Users will have to register directly on the relevant page.

https://letsencrypt.org/2025/01/22/ending-expiration-emails/

This change necessitates several updates to the documentation, particularly concerning the email field on Let’s Encrypt-related pages.

According to RFC 8555, operator notifications are optional. However, it might be prudent to retain the email field unless Let’s Encrypt is the sole ACME-provider entity utilizing it. Here’s the relevant excerpt from the RFC :

Once the CA is satisfied, it issues the certificate, and the ACME
client automatically downloads and installs it, potentially
notifying the operator via email, SMS, etc.

What are your thoughts on potentially removing the email field from the documentation and, possibly, from the cert-manager certificate controller itself ? In any case, I think it's important to deprecate this feature in the first instance for Let's Encrypt content.

I’m happy to create a PR for this, but I believe the approval and guidance of the cert-manager maintainers are essential before proceeding with any development.

Have a great day :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant