this post was submitted on 05 Jan 2026
346 points (99.4% liked)
PC Gaming
14361 readers
299 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is a surprisingly common issue. I've had it happen at least once in every job I've worked. This is usually the responsibility of the devops or devsec teams, and they are usually heavily underfunded since they are cost centers that do not bring in profit.
I work in DevOps, this is one of the easier things to automate. It's common for certs to be issued on a 90 day basis these days, no way that would be maintainable without automating.
Cool story if everything you have has an API or code based. Try doing it on hundreds of switches and other embedded devices. The whole 42 day thing they’re floating is gonna be a massive nightmare because they don’t realize all the other things out there that use certificates.
What makes you think I don't do this on embedded devices? I'm not about to dox my self with specifics, but I do this exclusively for embedded hardware as my job. We even do it for devices not directly attached to our network. It's really not difficult so long as you have control of your enterprise hardware (which, you should, unless your management is terrible at their jobs). Hell, even the routers we use have this functionality built in, failure alarms and all.
If this is a problem for you, it's probably at an organizational level, and not a technical issue.