190
Sysadmins slam Apple’s SSL/TLS cert lifespan cuts
(www.theregister.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Oct 2024
190 points (91.3% liked)
Technology
58792 readers
3182 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- 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, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Any post/article with the word “slammed” in it gets a downvote and a no-read from me. That word needs to disappear from journalism/forums/life/etc.
This is the one case where I'd make an exception. I read through the threads, it got particularly heated.
As someone who creates custom domain name applications, FUCK THEM WITH A PINEAPPLE SPIKY SIDE FIRST. This problem is on par with timezones for needless complexity and communication disasters. Companys and advertisers are now adding man in the middle certs for additional data collection/visibility. If the ciphers not cracked, changing the certs exposes significantly more failure, than letting one get a little stale.
Sysadmin used slam! It's super effective!
Why not just autorenew on a schedule?
I use Lets Encrypt, and my certs get renewed automatically without me thinking about it.
Mostly customer provided certs, high end clients make all kinds of stupid requests like the aforementioned man-in-the-middle chain sniffers, clients that refuse DNS validation, clients that require alternate domains to be updated regularly. Management is fine for mywebsite.com, but how are you solving an EV on the spoofed root prod domain, with an sso cert chain for lower environments on internal traffic that is originally provided by a client? And do you want the cs reps emailing each other your root cert and (mistakingly) the key? I've been given since SCARY keys by clueless support engineers. I don't want to do this every 3 months.
Sounds like a change in company policy, because AFAIK, there's no good reason for pretty much any of that.
Sounds like you don't do contact negotiations, if someone will pay 2 million to appear on their root domain, you'll sit down and figure it out for a couple hours.
Yes, I don't, and I would honestly like to understand what use-case these customers are trying to solve. Because there's a very good chance that they can get their preferred outcomes with a lot less manual work.
Unrelated to the topic, but I deal with a database storing timestamps.
In local time.
For systems all around the world.
You'll see current entries timestamped 12:28 from eastern Europe followed by ones 6:28 from America and then another 11:28 from central Europe.
Without offset.
Ew. Just store UTC timestamps and do optional translation on the client using whatever the client sets up for their timezone. It's not hard...
Oh believe me, I would change some things about that database if I could. Alas, I'm just the analyst building data models from it.
(To be fair, it's otherwise easy to work with and for most use-cases, it doesn't matter since they're aggregated per month anyway, so I just load the last month's data on the 2nd of each month. I definitely have worse patients to operate on.)
The Register is deliberately tabloid-like in style (right up to the "red top" site banner), but is good quality (at least when I read it).
They won't write an article about science without using the word "boffins" either. It's just their thing.