Elektrine lite

← Feed

@stratself@lemdro.id

2026-10-06 17:57 UTC

Anyone using 6-day certs yet? Since the beginning of this year, Let’s Encrypt rolled out a new shortlived profile for certificates that make them valid for only 160 hours. The intention, as they say, is to encourage automation and reduce the window of certificate compromise (because revocation is somewhat a flakey thing). Yet, I haven’t seen a lot of news about it since then. Hence the question: is this shorter cert thingy something you considered and deployed for your homelab? As for me I’ve set up lego-acme with profile: “shortlived” on my rig. Lego runs on a bihourly cronjob, but only renews when a cert has >=3 days to expiry. It’s been pretty much a set-and-forget experience, although some more monitoring would be nice.

Replies (7)

  • @observantTrapezium@lemmy.ca 2026-10-07 04:52

    No, and if there was an option for a 20-year certificate I would have taken it.

    Open ##5028466

  • @haroldfinch@feddit.nl 2026-10-06 18:26

    Thank you for sharing. I had missed the announcement, so pleased to know the option is available. I have fully automated the creation and renewal of my certs and have just short of 50 certs that I manage in total. Every single one automated using NixOS / ACME / lego. Technically I could easily implement this, just have to switch my config. Honest question, are there any particular security benefits to this (especially for a home lab)? I can understand the short lived time span further reduces risk of compromise, yet the existing time span is already “much shorter than traditional certificates”. Does it have a substantial impact on our security posture?

    Open ##5030837

  • @Decronym@lemmy.decronym.xyz 2026-10-07 05:50

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread: Fewer Letters More Letters CA (SSL) Certificate Authority TLS Transport Layer Security, supersedes SSL VPN Virtual Private Network [Thread #119 for this comm, first seen 7th Oct 2026, 05:50] [FAQ] [Full list] [@Two9A@hachyderm.io] [Source code]

    Open ##5031301

  • @Auli@lemmy.ca 2026-10-07 05:51

    Yes, with Caddy and haven’t noticed a thing, and had no complaints. So it has been perfectly fine and it is all automated.

    Open ##5031338

  • @tburkhol@slrpnk.net 2026-10-06 19:07

    I’m happy with 90 day certs for homelab stuff: I’m not worried about anyone MITMing my network. I figure the short lived certs are more important for people who provide services with a significant external user-base, or who process sensitive transactions. I have my certbot set to check every 12 hours and renew at 60 days. Renewing every 3 days would be 20x more load on Let’s Encrypt systems, and that feels like abuse of a free service for my use case.

    Open ##5031414

  • @sonstwas@sh.itjust.works 2026-10-06 19:15

    Honest, non-techie question: How is it an advantage? Given modern crypto isnt it more likely that a mitm didn’t crack the crypto but instead got somehow else in the middle and just can “ignore” certs renewals?

    Open ##5031509

  • @antsu@discuss.tchncs.de 2026-10-06 20:35

    I migrated from vanilla Nginx Proxy Manager to NPMplus (because of CrowdSec), and it defaults to short-lived certificates. Other than temporarily making my Uptime Kuma SSL monitors completely freak out because my certificates “were too close to expiration”, everything still works exactly the same.

    Open ##5035243