Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Hp Client Security Manager problem (Add-ons)

  • 1 wotmołwa
  • 87 ma tutón problem
  • 90 napohladow
  • Poslednja wotmołwa wot Paul

more options

In Mozilla Firefox 32.00 version I have easily used Hp Client security manager for finger-print login. Next I updated the Firefox 46.0b10 and again another. But now this moment I can not use Hp Client security Manager. In Add-ons Extensions showing message: Hp Client Security Manager could not be verified for used in Firefox and has been disabled. So, How can I verify Hp Client Security Manager for use in Firefox?

In Mozilla Firefox 32.00 version I have easily used Hp Client security manager for finger-print login. Next I updated the Firefox 46.0b10 and again another. But now this moment I can not use Hp Client security Manager. In Add-ons Extensions showing message: Hp Client Security Manager could not be verified for used in Firefox and has been disabled. So, How can I verify Hp Client Security Manager for use in Firefox?

Wubrane rozrisanje

Hi

Between the two versions of Firefox that you mention, additional security has been put in place to protect people from malicious add-ons. This has involved the add-on developer (the person that made the add-on) applying to Mozilla to get it verified.

Many add-ons developed by small groups of individuals have completed this without a problem, however some people (including some large companies) have used this as an opportunity to remove support from an add-on they no longer wish to provide.

I recommend that you contact HP who should be able to provide more information and possibly an alternative solution.

Tutu wotmołwu w konteksće čitać 👍 3

Wšě wotmołwy (1)

more options

Wubrane rozrisanje

Hi

Between the two versions of Firefox that you mention, additional security has been put in place to protect people from malicious add-ons. This has involved the add-on developer (the person that made the add-on) applying to Mozilla to get it verified.

Many add-ons developed by small groups of individuals have completed this without a problem, however some people (including some large companies) have used this as an opportunity to remove support from an add-on they no longer wish to provide.

I recommend that you contact HP who should be able to provide more information and possibly an alternative solution.