Why does it take a team of highly competent people (lol) working around the clock to update a certificate and...

>Mark my words they are using this as an excuse to mass flag specific addons that were previously approved that they dont want renewed.
Like what the only two addons i really care about are noscript and ublock and no way they would block those 2 they are even in the promoted page

Nigga I dont give a fuck about what Jow Forums thinks. 2 years ago was when the initial addon purge happened right? When they broke support for all previous addons
You can call me a conspiratard if you like, but that doesnt make it any less sketchy that they do this, then the only solution they offer to fix it is turning on telemetry studies.

You're misunderstanding the problem
You're only half right
The problem is that Firefox has a built-in ballpoint pen which can magically only be used by Firefox to sign off that an add-on has not been tampered with. This pen, which has been around since FIrefox 42, ran out of ink today and now needs to be replaced. There is a hotfix which will replace the pen with a new one, but this is only temporary as that pen will again run out of ink eventually. The fags over at Mozilla don't want to push a real patch which adds a new pen for a reason which I have not bothered to understand. Probably because they are trying to include a permanent fix in the patch which will add some functionality for automatically replacing the pen in the future.

There was no change.
A security certificate that firefox relied on had an expiration date and it expired today.

If traveled back in time to the release date of FF42 and set your computer's clock to May 04 2019, it would break just as much.

>2 years ago was when the initial addon purge happened right? When they broke support for all previous addons
It was way before that user, that happened in Fx 57, this feature got introduced in Fx 48
>then the only solution they offer to fix it is turning on telemetry studies.
Yeah, this is what adds insult to injury, they didn't even disable running studies so you would get studies (which don't get disabled after unchecking the studies checkbox) alongside the fix
The manual fix that doesn't involve enabling studies was posted by third parties on places like the Hacker News comments
I'm not a retard dumb faggot, I'm not against extension signing, however I was and still am against disabling the possibility to disable signing checks
>for a reason which I have not bothered to understand
The add-on update logic permanently disables any extension whose certificate has expired, that's why the fix isn't trivial
>permanent fix in the patch which will add some functionality for automatically replacing the pen in the future.
This completely defeats the point of signing extensions

The possibility to disable signing checks is still available in the dev version, so if you actually need that functionality you should probably use that. And no, automatically updating the certificate does not defeat its purpose. Since only Mozilla can replace it there is no difference whether they do it manually or automatically. (Although I was only guessing that they'd be adding that kind of functionality anyway)

>The possibility to disable signing checks is still available in the dev version
Yeah, and on Nightly and ESR too, but not on stable which is what the majority of users run
>so if you actually need that functionality you should probably use that
So I'm at the mercy of Mozilla trannies who can't even renew their certs?
>automatically updating the certificate does not defeat its purpose
It does if it is done locally
> Since only Mozilla can replace it there is no difference whether they do it manually or automatically. (Although I was only guessing that they'd be adding that kind of functionality anyway)
There's no need to add this functionality client side, pretty much anyone who is sane automatically renews certs, except for the incompetent fucks at Mozilla
Either way, automatically renewing certs doesn't need an user side update

Most people are very, VERY stupid about SSL certificates and PKI. Even most programmers at major tech companies are. Mozilla should really be pulling the latest cert periodically from a known URL rather than shipping it with no way to update, and I suspect they're struggling with that change like retards as described in .

This is a client side cert. Mozilla has to get it to their users somehow.

Still sounds pretty gay. My old addons all died for this nu-firefox. The people who programmed them are probably old men or dead by now. I have no faith in the current generation to make.anything decent

It's already done through the update mechanism Firefox uses for add-ons

To be clear, I'm not defending them and I think this is an amazing failure on their end. You may need a client-side update for such functionality in order to allow the client to receive such an update. In other words, if the certificate is completely baked in and there is no remote way to replace it with a new one then client functionality needs to be developed. I'm not saying to generate it on the client, as that would require Mozilla's private key.

The problem with the old addons, and the entire reason Chrome exists, is that you can't do multiprocess or sandboxing when extensions have full access to the browser's internals and it assumes single process.

Because of the diversity hires.

Attached: Screen_Shot_20190503_at_11.31.21_PM.png (1200x424, 135K)

What a bunch of incompetent boobs.

AAAAAAAAAAAAAAAAAAAAAAHHHHH

WHAT IS HAPPENING!!!!

WHY MY EXTENSIONS DON'T WORK!