There were no Firefox updates that did this nor some ulterior conspiracy theory of motives blah blah ...greybeard2012 wrote:This stinks not only of an extension disabling enforcement but also a Firefox update enforcement too.
People were blaming Fx 66.0.3 even though it was released back on April 10th.
It was an unfortunate case of a intermediate certificate that well expired and many extensions were affected.
https://blog.mozilla.org/addons/2019/05 ... n-firefox/
The 66.0.4 and 60.6.2esr updates are not proof that it was indeed a Firefox problem but rather as a way to get people using their extensions again.