

Firefox Certificate Expiration Threatens Add-ons, Streaming on March 14 (betanews.com) 30
A critical root certificate expiring on March 14, 2025 will disable extensions and potentially break DRM-dependent streaming services for Firefox users running outdated browsers. Users must update to at least Firefox 128 or ESR 115.13+ to maintain functionality across Windows, macOS, Linux, and Android platforms.
The expiration additionally compromises security infrastructure, including blocklists for malicious add-ons, SSL certificate revocation lists, and password breach notifications. Even those on legacy operating systems (Windows 7/8/8.1, macOS 10.12â"10.14) must update to minimum ESR 115.13+.
The expiration additionally compromises security infrastructure, including blocklists for malicious add-ons, SSL certificate revocation lists, and password breach notifications. Even those on legacy operating systems (Windows 7/8/8.1, macOS 10.12â"10.14) must update to minimum ESR 115.13+.
Not for distro handling certs (Score:5, Informative)
Re:Not for distro handling certs (Score:5, Interesting)
firefox use their own CA management, outside the system CA store. This is both great (as solves weird problems and make sure firefox behaves the same and rogue CA certs aren't really used unless the user also install them directly in firefox), but also bad, as a system update do not update firefox CA side
Not sure if iceweasel was patch to use the system CA store
Re: (Score:3)
Also, yes, Firefox in Debian is patched to use the "ca-certificates" package CA store. The funny bit is that this ca-certificate is built using the certificates from
Certificate expiries are timebombs (Score:5, Insightful)
Re: (Score:2)
It should be easier than this to manually update the certificate store on any program or automate it with third party utiltiies.
Seems that Firefox will only trust private root stores from the operating system and they don't intend to ever support using the rest of the store from the OS. Of course that doesn't help when the OS is obsolete too, but it would be much easier to import updated certs once at the OS level instead of to each individual app.
Re: (Score:2)
All OS use their own way to manage CA and mozilla always used their own CA store to workaround that. It is also safer, as rogue CA will not be used, someone have to manually install those in firefox too. Firefox does a good job updating their CA store... as long users also update their browsers.
Being so complex, no one should use out of date browsers, but even if you really need to run one old browser, nothing blocks you from loading the missing update CA in that browser too, but them is up to you maintain
Re: (Score:3, Insightful)
Mozilla won't lift a finger to solve this self-imposed problem.
They instead DEMAND users switch browsers... to something that still runs on old computers. Not everybody runs old computers and old software on their WAN, there is plenty of LAN only computer usage out there. Even so, it's the user's freedom and they need to stop forcing their will on others. It's what drove a lot of users away from Firefox in the 1st place.
What a self entitled crybaby (Score:3)
They wrote this software for free, and they gave you for free security updates that don't require accepting any new features. They even went out of their way to continue putting out security releases (ESR 115.13) for operating systems that Microsoft and Apple don't even support anymore. And they did this all six months in advance so you would have plenty of time to upgrade.
But enjoy your freedom to run old unpatched software.
Re: (Score:2)
If only it was open source and you could fix it yourself...
Not that it matters. If Mozilla pushes an update for the older browser, the mouth-breathers will bitch and moan about Mozilla "wasting resources" on old versions that no one uses instead of "fixing" their pet problem that either never existed or was fixed 10+ years ago. The five or six people actually affected will bitch and moan about how they're being "forced" to install a patch with a "why can't they just leave things alone".
If you want to use
yep (Score:1)
What the hell is this crap!? (Score:1)
"10.12â"10.14"
It's 2025. I expected this in 1999. Seriously, sort out the encodings already.
Re: (Score:2)
Slashdot supports endashes and emdashes with – and — respectively.
There's absolutely no good reason for it not to recognize Unicode characters in story and comment submissions, translate the supported ones to entities, and strip the rest. That would be trivial and require zero backend changes.
Defending incompetence is now an American tradition, but it's still pathetic every time.
Re: (Score:2)
The moment Unicode gets supported you will see no end of drawn swastikas all over the fucking site.
Please think about abuse before you think about functionality. This is why so much software sucks - nobody does this.
Re: (Score:2)
I am asking for only and exclusively the primary glyphs matching the HTML entities which are allowed on the site, plus curly quotes and ticks which can be implemented the same way to solve the Mac user problem some way other than finally.
Re: (Score:2)
Mac users can easily set their keyboards to behave properly.
Re: (Score:2)
I actually meant iOS, sorry. And I know, they can turn off the feature too, but they aren't going to. Meanwhile, the rest of us have to deal with their output. But also, it would be of help while posting quotations.
Re: (Score:2)
I agree it's just fine the way it is right now, especially for an English only site. I never understood the bitching for unicode. Unicode brings in some security issues as well.
Re: (Score:2)
I agree, it's fine the way it is now, especially for an English only site. Unicode brings in some security issues as well.
Re: (Score:2)
They accept UTF-8 as a the content-type for submitting comments, then butcher the content by not supporting it.
Timing is everything (Score:4, Interesting)
Re: (Score:2)
you know that this kind of CA certificates have long expiration dates... this certificate is probably like for 10 or 20 or 25 years...
call that conspiracy, planing a forced user update to a new term of services by starting to use something 10 years ago, just yo catch you now!!
Re: (Score:1)
You're insane.
The "terms of use" non-issue was a whole lot of nonsense from people who didn't understand the TOS, and a bunch of idiots that blindly repeated the bullshit. You have nothing to worry about w.r.t. Firefox and your privacy. Get a clue. [mozilla.org]
Re: Timing is everything (Score:2)
Re: (Score:2)
You're lying about the TOS. Firefox did nothing wrong. We also need Firefox for a healthy web. Spreading bullshit like you're doing is only going to help Google completely take over the browser market, which, as we've seen, will bring to life all of your paranoid delusions and more.
Don't be corporate tool.
Re: (Score:2)
>"Seems like this might have been factored in with the terms of use change [...]"
-1 Troll or at least -1 Overrated
The terms of service thing was a big-hype nothing-burger.