Why has my Kaspersky protection add on no longer working/acceptable to Firefox when it worked until last week?
The add on, Kasperky 4.6.2.23.1 has been disabled but has been working fine until last week. I cannot believe that Kaspersky has gone through the process that Mozilla require or shouldn't they recognise established companies such as Kaspersky.
Isisombululo esikhethiwe
The "rules" apply to Kaspersky as much as any other add-ons developer - if an extension isn't "signed" Firefox 43 will disable it.
That said there is a temporary solution that might work.
There's an add-on - https://addons.mozilla.org/fr/firefox/addon/install-unsigned-add-ons/ - to "automate" this procedure.
Override add-on signing (advanced users): You can override this setting by changing the xpinstall.signatures.required preference to false in the Firefox Configuration Editor (about:config typed in the URL bar). Support is not available for any changes made with the Configuration Editor so please do this at your own risk.
Note: That pref will be gone in Firefox 44 (Release slated for Jan 26. 2016) so user's of currently un-signed extensions should contact the developers of those extensions and prod them into getting their act together & get their extensions signed by Mozilla. Otherwise the users of those extensions will be SOL come the release of Firefox 44. Mozilla has already pushed back the version in which this new security feature was to be enabled from Firefox 40 to 44. I doubt if there will be any further reprieve.
Funda le mpendulo ngokuhambisana nalesi sihloko 👍 16All Replies (2)
Isisombululo Esikhethiwe
The "rules" apply to Kaspersky as much as any other add-ons developer - if an extension isn't "signed" Firefox 43 will disable it.
That said there is a temporary solution that might work.
There's an add-on - https://addons.mozilla.org/fr/firefox/addon/install-unsigned-add-ons/ - to "automate" this procedure.
Override add-on signing (advanced users): You can override this setting by changing the xpinstall.signatures.required preference to false in the Firefox Configuration Editor (about:config typed in the URL bar). Support is not available for any changes made with the Configuration Editor so please do this at your own risk.
Note: That pref will be gone in Firefox 44 (Release slated for Jan 26. 2016) so user's of currently un-signed extensions should contact the developers of those extensions and prod them into getting their act together & get their extensions signed by Mozilla. Otherwise the users of those extensions will be SOL come the release of Firefox 44. Mozilla has already pushed back the version in which this new security feature was to be enabled from Firefox 40 to 44. I doubt if there will be any further reprieve.
Thanks for the swift response and help.