Conversation
jmorris

James Morris

"We’re writing to inform you that we intend to discontinue sending expiration notification emails. " https://letsencrypt.org/2025/01/22/ending-expiration-emails/

Understandable, but I'm guessing this will cause a lot of breakage for a while & train people to click through browser security warnings. Thoughts?
1
0
0
securepaul@fosstodon.org

Paul Moore

Reply to @jmorris

@jmorris Agreed. I understand why they are doing it, and I recognize that for many people email isn't a reasonable notification mechanism, but I personally am going to miss this and I worry about the impact it will have in approximately three months.

1
0
0
monsieuricon

K. Ryabitsev

Reply to @securepaul@fosstodon.org
@securepaul @jmorris I believe it's more like "we're tired fighting with your email providers."
1
0
4
securepaul@fosstodon.org

Paul Moore

Reply to @monsieuricon

@monsieuricon @jmorris Yeah, like I said, I understand why, but that doesn't mean I'm not sad to see it go away.

1
0
0
kees@fosstodon.org

Kees Cook tux

Reply to @securepaul@fosstodon.org

@securepaul @monsieuricon @jmorris I didn't even know this feature existed! I'm genuinely curious, though: doesn't everyone using certbot just automatically renew? (And don't orgs who need to care about service availability already have an external status checking system?) Again, I'm not trying to be obtuse, but how were these emails used?

3
0
0
monsieuricon

K. Ryabitsev

Reply to @kees@fosstodon.org
@kees @securepaul @jmorris It's true that certbot will auto-renew, but things do go wrong with the process every now and again (especially if you use DNS-based proofs). So, having a "btw, your TLS cert is about to expire" email was a good last-resort measure to prevent a much worse oh-shit moment. :)
1
0
2
corbet

Jonathan Corbet

Reply to @kees@fosstodon.org
@kees @securepaul @monsieuricon @jmorris I have found them to be really useful when, for whatever reason, the automatic renewal process breaks and the cert heads toward expiration. Maybe I'm just clumsy, but I have managed to break it a time or two without noticing.

Yes, we should just have some sort of monitoring of our own ... that's gonna be happening soon ...
2
2
4
securepaul@fosstodon.org

Paul Moore

Reply to @monsieuricon

@monsieuricon @kees @jmorris Yes, exactly. All of my systems happily auto-renew as expected, but there have been cases in the past where something on the system changed and auto-renew stopped working.

The emails were a nice sanity check.

0
0
0
monsieuricon

K. Ryabitsev

Reply to @corbet
@corbet @kees @jmorris @securepaul Don't feel bad, it literally happened to me last week with www.kernel.org because there was a DNS record clash. ;)

(But we do have monitoring in place, so we caught it that way.)
0
0
4
Anarcat@kolektiva.social

anarcat

Reply to @corbet

@corbet you have thousands of readers monitoring that site: don't worry, you'll know if your certs expire. ;)

0
0
0
mcdanlj@social.makerforums.info

Michael K Johnson

Reply to @kees@fosstodon.org

@kees @securepaul @monsieuricon @jmorris I have one server where I've done something that breaks certbot, I don't know what, and have never investigated. I just manually renew when I get the email. Lazy me.

I guess I have some debugging in my future.

0
0
1
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: