X
Tap here to go to the mobile version of the site.
Scheduled maintenance: Thursday, April 2, between 3pm and 5pm UTC. This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn’t solve your issue and you want to ask a question, we have our support community waiting to help you at @firefox on Twitter

منتدى الدعم

Why has my Kaspersky protection add on no longer working/acceptable to Firefox when it worked until last week?

Posted

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.

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.

Chosen solution

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.

https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox#w_what-can-i-do-if-firefox-disables-an-installed-unsigned-add-on

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.

Read this answer in context 16

Additional System Details

Installed Plug-ins

  • Citrix Online App Detector Plugin
  • HPDetect
  • Intel web components for Intel® Identity Protection Technology
  • Intel web components updater - Installs and updates the Intel web components
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • Next Generation Java Plug-in 11.45.2 for Mozilla browsers
  • The plugin allows you to have a better experience with Microsoft SharePoint
  • The plugin allows you to have a better experience with Microsoft Lync
  • Nitro PDF plugin for Firefox and Chrome
  • NPWLPG
  • Shockwave Flash 20.0 r0
  • Adobe Shockwave for Director Netscape plug-in, version 11.6.5.635
  • 5.1.41105.0
  • Skype Web Plugin 7.9.0.56
  • VLC media player Web Plugin
  • WildTangent Games App V2 Presence Detector

Application

  • Firefox 43.0.1
  • User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
  • Support URL: https://support.mozilla.org/1/firefox/43.0.1/WINNT/en-US/

Extensions

  • Evernote Web Clipper 6.1 ({E0B8C461-F8FB-49b4-8373-FE32E9252800})
  • KidStart Savings Prompt 1.0.4.8 (KidStart@KidStart)
  • SaveFrom.net - helper 5.76 (helper-sig@savefrom.net)
  • Garmin Communicator 4.2.0.0 ({195A3098-0BD5-4e90-AE22-BA1C540AFD1E}) (Inactive)
  • iSkysoft iMedia Converter Deluxe 5.1.0 (ISVCU@iSkysoft.com) (Inactive)
  • Kaspersky Protection 4.6.2.23.1 (light_plugin_D772DC8D6FAF43A29B25C4EBAA5AD1DE@kaspersky.com) (Inactive)
  • Wondershare Video Converter Ultimate 7.1.0 (WSVCU@Wondershare.com) (Inactive)

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription: Intel(R) HD Graphics 4000
  • adapterDescription2:
  • adapterDeviceID: 0x0166
  • adapterDeviceID2:
  • adapterDrivers: igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32
  • adapterDrivers2:
  • adapterRAM: Unknown
  • adapterRAM2:
  • adapterSubsysID: 183f103c
  • adapterSubsysID2:
  • adapterVendorID: 0x8086
  • adapterVendorID2:
  • direct2DEnabled: True
  • directWriteEnabled: True
  • directWriteVersion: 10.0.10586.0
  • driverDate: 8-17-2015
  • driverDate2:
  • driverVersion: 10.18.10.4276
  • driverVersion2:
  • info: {u'AzureCanvasBackend': u'direct2d 1.1', u'AzureFallbackCanvasBackend': u'cairo', u'AzureContentBackend': u'direct2d 1.1', u'AzureSkiaAccelerated': 0}
  • isGPU2Active: False
  • numAcceleratedWindows: 1
  • numTotalWindows: 1
  • supportsHardwareH264: Yes
  • webglRenderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 4000 Direct3D11 vs_5_0 ps_5_0)
  • windowLayerManagerRemote: True
  • windowLayerManagerType: Direct3D 11

Modified Preferences

Misc

  • User JS: No
  • Accessibility: No
the-edmeister
  • Top 25 Contributor
  • Moderator
5433 solutions 40564 answers

Chosen Solution

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.

https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox#w_what-can-i-do-if-firefox-disables-an-installed-unsigned-add-on

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.

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. https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox#w_what-can-i-do-if-firefox-disables-an-installed-unsigned-add-on '''Override add-on signing (advanced users):''' You can override this setting by changing the '''xpinstall.signatures.required''' preference to '''''false''''' in the [https://support.mozilla.org/en-US/kb/about-config-editor-firefox 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.

Thanks for the swift response and help.