this post was submitted on 17 Apr 2025
200 points (98.1% liked)
Technology
69211 readers
3179 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
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
I'm that poor bastard engineer at my company. This likely will be the push we need to prioritize automation. Dealing with manual renewals with Digicert has been a pain in the ass. If anyone has experience with their automated option I'd love to hear it.
Aren't they RFC8555-compatible?
Yep, seems so:
If you search for RFC8555 or ACME, you may find a tool you can use that may be compatible for renewing Digicert certs automatically.
I'd love to actually help, but honestly I knew the RFC offhand (correction; I was close but off) and googled the rest myself, so dragging the problem to ACME - like RFK dragging the carcass of a deer back to his sedan - is the best I can do for you today.
Ironically the shortening of cert lengths has pushed me to automated systems and away from the traditional paid trust providers.
I used to roll a 1-year cert for my CDN, and manually buy renewals and go through the process of signing and uploading the new ones, it wasn't particularly onerous, but then they moved to I think either 3 or 6 months max signing, which was the point where I just automated it with Let's Encrypt.
I'm in general not a fan of how we do root of trust on the web, I much prefer had DANE caught on, where I can pin a cert at the DNS level that is secured with DNSSEC and is trusted through IANA and the root zone.
I've proposed using Let's Encrypt but my coworkers believe there would be a perception issue with us using a "free" TLS certificate provider. I work for a popular internet search engine so it's a reasonable worry.
It just seems like LE has the most efficient automatic renewal setup, though I haven't looked in detail at other providers.
That sound weird to me. How big is the population of people who are technical enough to even check what certificate provider you are using but ignorant enough to think that let's encrypt is bad because it's free?
There can be theoretical audit or blame issues , since you're not "paying" then how does the company pass the buck (SLA contracts) if something fucks up with LE.
Managers.
LetsEncrypt also built ACME, so they're the primary port for testing RFC8555. They're just gonna work better at it.
But, as above, maybe Digi is still the way for you, with the right tooling glued in.
Good luck!