ALL add-ons will stop working on Firefox versions older than 128 (or older than ESR 115.13+) on March 14, in just a few days from now. To keep using your add-ons update Firefox | EFF/Privacy Badger (bsky.app)
from AlolanVulpix@lemmy.ca to privacy@lemmy.ca on 12 Mar 15:56
https://lemmy.ca/post/40533796

Privacy Badger on Bluesky

Using an older version of Firefox?

ALL add-ons will stop working on Firefox versions older than 128 (or older than ESR 115.13+) on March 14, in just a few days from now.

To keep using your add-ons including Privacy Badger, you will need to update Firefox: …mozilla.org/…/root-certificate-expiration

#privacy

threaded - newest

Showroom7561@lemmy.ca on 12 Mar 16:16 collapse

Jesus, if you’re still using a browser that like 10 major versions old, you’ve got bigger problems than worrying about a privacy plugin no longer being supported!

AlolanVulpix@lemmy.ca on 12 Mar 16:20 next collapse

It’s all add-ons, not just Privacy Badger.

Showroom7561@lemmy.ca on 12 Mar 16:54 collapse

Ah, I thought it was add-ons by that developer.

But still, nobody should be on such an old build of any browser - for security and privacy sake.

LWD@lemm.ee on 12 Mar 18:46 collapse

I wonder how this will effect Pale Moon.

Showroom7561@lemmy.ca on 12 Mar 19:05 collapse

Their changelogs seem to be pretty up-to-date, so I would assume they are on the latest FF codebase, no?

LWD@lemm.ee on 12 Mar 19:23 collapse

It’s long been departed from the Firefox codebase.

My ponderings did end up being pointless, though: it turns out they never even supported MV2 Firefox extensions.

corsicanguppy@lemmy.ca on 12 Mar 20:00 next collapse

Or you have an extended OS support contract. And that’s something even small biz uses. Er, so I’ve heard.

But carry on. Stale stuff is bad stuff, apparently, but I can see 7 rail lines from my window.

i_am_not_a_robot@discuss.tchncs.de on 12 Mar 22:00 collapse

Extended OS support has little to do with using outdated browsers. Firefox 115.13 should run on any OS that can run 115.12 and it doesn’t have this problem. Versions older than 115.21 have critical security vulnerabilities and should not be used in an environment where they could load untrusted content from the internet.

swordgeek@lemmy.ca on 13 Mar 01:07 collapse

Jesus, if you’re still using a browser that like 10 major versions old, you’ve got bigger problems than worrying about a privacy plugin no longer being supported!

Versions are meaningless. It’s just numbering.

128 came out in July of last year, which means that Firefox will deliberately block use of products after eight months.

That’s fucking garbage. Software development and release lifecycles have turned into a “release-ignore-discontinue” cycle of barely long enough for consumers to constantly upgrade to.

Showroom7561@lemmy.ca on 13 Mar 01:50 next collapse

128 came out in July of last year, which means that Firefox will deliberately block use of products after eight months.

Is there a way to find out how many security specific fixes were introduced in those 8 months?

I would agree with you only if the version updates were purely cosmetic, but I tend to see security patches with nearly every release. And 8 months sounds like an eternity to not be patched up.

AlolanVulpix@lemmy.ca on 13 Mar 02:48 collapse

They aren’t deliberately blocking anything, but rather certificates are expiring.