Hi,
I am using Firefox 78.15.0esr (64-bit) on a 16+ year old MacMini with el Capitan. I use it for various low performance use cases like playing music, and for testing … (lire la suite)
Hi,
I am using Firefox 78.15.0esr (64-bit) on a 16+ year old MacMini with el Capitan. I use it for various low performance use cases like playing music, and for testing the performance of my webapplications on old hardware, using outdated software
Reading the attached message (and followed up information page), I understand that I can still use this version of Firefox. But that all add-ons will be disabled in two months. Which is very upsetting to say the least. Why is a stand-alone add-on that doesn't communicate with an outside server being disabled?
Given that I run an unsupported(?) version of MacOS which I can not upgrade, I won't be able to update Firefox to the version that is being suggested. This means that Mozilla (the party that I've always cheered on for its vision), now remotely limits my access to the internet because of a certificate that they used in the development of the software becomes obsolete. This is a move that I'd expect from Google, Microsoft or Apple, but not from Mozilla.
Could someone with a more technical background explain me how such a certificate is related/integrated in the build of Firefox (78). I mean, why isn't it possible to re-build the project with a newer root certificate, given all of the source files are online: https://archive.mozilla.org/pub/firefox/releases/78.0/ ?