News for hackers. Stuff that matters.
Re:Let's Encrypt: Reliability via Automated Renewal Information by lisper on Friday March 24, 2023 @02:57PM (#35293848)
> by definition you already automated the renewal process on a schedule too

No, certbot does not run on a schedule by default. You have to set that up separately, and that can be non-trivial because you have to be able handle failures.

Re:Let's Encrypt: Reliability via Automated Renewal Information by schoen on Friday March 24, 2023 @02:59PM (#35293881)
If you installed it with pip, it doesn't; if you installed it with an OS package or snap, it does (although it also didn't in that case for about the first year and a half of its existence, I think).
Re:Let's Encrypt: Reliability via Automated Renewal Information by tomxor on Friday March 24, 2023 @03:52PM (#35294540)
Can confirm, I have been using certbot+apache in production across multiple servers from Ubuntu apt repos since 18.04 in 2018 and scheduled auto-renewal is the default.
Re:Let's Encrypt: Reliability via Automated Renewal Information by cm2187 on Friday March 24, 2023 @03:02PM (#35293916)
But if certbot doesn't run on schedule, presumably it will never connect to ARI either.
Re:Let's Encrypt: Reliability via Automated Renewal Information by mholt on Friday March 24, 2023 @03:52PM (#35294539)
This is why Certbot should only be used temporarily to transition from legacy infrastructure. Ideally cert management (ACME client) needs to be baked into the server, like what Caddy does.
Re:Let's Encrypt: Reliability via Automated Renewal Information by adql on Friday March 24, 2023 @04:12PM (#35294788)
About the last thing security-wise that I want is for http server to control DNS record (which is required to have wildcard certs in LE)
Re:Let's Encrypt: Reliability via Automated Renewal Information by mholt on Friday March 24, 2023 @06:03PM (#35296272)
When done properly, this is less of an attack vector than you think (certainly much less than a phishing email).