Date: Tue, 7 May 2019 12:11:02 +0100 From: Arthur Chance <freebsd@qeng-ho.org> To: Dave B <g8kbvdave@googlemail.com>, freebsd-questions@freebsd.org Subject: Re: firefox 66.0.3 disables noscript Message-ID: <16d62dc9-dd1f-57ee-287e-2618f0309c50@qeng-ho.org> In-Reply-To: <26069e39-44e4-42d7-aaaa-581c92afa8bf@googlemail.com> References: <mailman.106.1557144002.2568.freebsd-questions@freebsd.org> <26069e39-44e4-42d7-aaaa-581c92afa8bf@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/05/2019 09:14, Dave B via freebsd-questions wrote: > You can tell FF not to check certificates for add-on's, without > affecting the usual certificate system. > > That is what I did to "restore" add-on functionality. (But I only have > one, "Ublock Origin", replaces addblock+ and no-script. Very low impact > and no need to continually faff about with scriping settings.) > > ~ ~ ~ > > From ZDnet:- > > For Firefox users that are currently impacted by this bug, an easy > workaround would be to visit the about:config section and set > xpinstall.signatures.required to false. This disables the extension > signing mechanism in Firefox, the system through which the browser > verifies that the local extension is one that's been installed from the > central Mozilla Add-ons repository --and for which the signing > certificate had expired. > > ~ ~ ~ > > However, it's now fixed, in other major OS version of FF, so perhaps > someone needs to update the F'BSD version. It was updated in ports two days ago https://www.freshports.org/www/firefox/ -- What do we want? A time machine! When do we want it? Errm ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16d62dc9-dd1f-57ee-287e-2618f0309c50>