4 ms·
My case, I have to manage a portal for old tvs and those don’t accept the LE root certificate since they changed a couple of years ago. Unfortunately the vendor
by joking 10mo ago
My case, I have to manage a portal for old tvs and those don’t accept the LE root certificate since they changed a couple of years ago. Unfortunately the vendor is unable to update the firmware with new certificates and we are sold
- aftbit 10mo agoYeah that LE root certificate change broke our PROD for about 25% of traffic when it happened. Everyone acts like we control our client's cert chains. Clients don't look at the failure and think "our system is broken - we should upgrade". They look at the connection failure and think "this vendor is busted - might as well switch to someone who works". I switched away from LE to the other free ACME provider for our public-facing certs after that.
- nickf 10mo agoRoots for all CAs are going to be rotating much more frequently now. Looking to be every 5 years.
- michaelt 10mo agoI'd be interested in hearing more - do you have a source for this? Seems to me CAs have intermediate certificates and can rotate those, not much upside to rotating the root certificates, and lots of downsides.
- nickf 10mo agoChrome root policy, and likely other root policies are moving toward 5-years rotation of the roots, and annual rotation of issuing CAs. Cross-signing works fine for root rotation in most cases, unless you use IIS, then it becomes a fun problem.
- mikestorrent 10mo agoWhat an absolute pain in the ass for a mediocre increase in security.
- aaomidi 10mo agoThe upside to rotating roots is: 1. These might need to happen as emergencies if something bad happens 2. If roots rotate often then we build the muscle of making sure trust bundles can be updated I think the weird amount they are being rotated today is the real root cause if broken devices and we need to stop the bleed at some point.
- selcuka 10mo ago> If roots rotate often then we build the muscle of making sure trust bundles can be updated Five years is not enough incentive to push this change. A TV manufacturer can simply shrug and claim that the device is not under warranty anymore. We'll only end up with more bricked devices.
- michaelt 10mo ago> 1. These might need to happen as emergencies if something bad happens Isn't this the whole point of intermediate certificates, though? You know, all the CA's online systems only having an intermediate certificate (and even then, keeping it in a HSM) and the CA's root only being used for 20 seconds or so every year to update the intermediate certificates? And the rest of the time being locked up safer than Fort Knox?
- aaomidi 10mo agoThe thing is even the most secure facilities need ingress and egress points. Those are weaknesses. It’s also that a root rotation might be needed for completely stupid vulnerabilities. Like years later finding that specific key was generated incorrectly.
- silverwind 10mo agoSounds like planned obsolescence if devices stop working after 5 years or less.
- majewsky 10mo agoOnly for devices that do not allow you to patch the CA bundle as an aftermarket repair. Call your representative and demand Right to Repair legislation.
- aftbit 10mo agoThat is ... basically all of them? Other than general purpose desktop/laptop computers that is. Show me a TV or smartphone that does allow you to push new roots to it...
- account42 10mo agoAnd your clients are right. The "security" community's wanton disregard for backwards compatibility is abhorrent.
- deepsun 10mo agoWell, how the vendor was going to apply other security updates if they cannot update their basic security trust store? If the vendor is really unable to update, then it's at best negligence when designing the product, and at worst -- planned obsolescence.
- lokar 10mo agoYeah, participation in web tls requires the ability to regularly update your server and client code. Nothing stays the same forever, software is never done. It’s absurd pretend otherwise.
- michaelt 10mo ago1. Ship the product with automatic updates delivered over https 2. Product is a smart fridge or whatever, reasonable users might keep it offline for 5+ years. 3. New homeowner connects it to the internet. 4. Security update fails because the security update server's SSL cert isn't signed by a trusted root.
- array_key_first 10mo agoThe real solution is making your shit modifiable by the client. We do car recalls all the time. Just send out an email or something with instructions of what to put on a USB, it's basically the same thing. Yes it's inconvenient for consumers and annoying but the alternative is worse. Essentially hard coding certificates was always a bad idea.