搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Why Are Some Add-Ons OK One Day And A Threat The Next?

  • 4 回覆
  • 2 有這個問題
  • 19 次檢視
  • 最近回覆由 James

more options

Hello,

Let me begin by saying that I adore Firefox and have great respect for the Mozilla Team and its minions.

However, I am a little upset that three add-ons that I use regularly and have for some time suddenly could not be verified by Firefox and so were summarily disabled all in the name of security. To be specific, these add-ons are: Advanced SystemCare Surfing Protection, Avast Online Security, and LastPass. I have no idea what chaged overnight to cause these particular add-ons to now be perceived as a threat, but I surmise that whatever blacklist you all are using has suddenly included these add-ons.

But what has me REALLY incensed is the fact that a means to allow these add-ons in spite of whatever security risk they may pose is not made immediately available for those of us who are willing to accept the risk of using an add-on that hasn't met your entirely arbitrary signing policy.

I don't really expect anyone to take any action to solve this problem even though I think you ought to. I hope you will let us know when the pissing contest is over.

Hello, Let me begin by saying that I adore Firefox and have great respect for the Mozilla Team and its minions. However, I am a little upset that three add-ons that I use regularly and have for some time suddenly could not be verified by Firefox and so were summarily disabled all in the name of security. To be specific, these add-ons are: Advanced SystemCare Surfing Protection, Avast Online Security, and LastPass. I have no idea what chaged overnight to cause these particular add-ons to now be perceived as a threat, but I surmise that whatever blacklist you all are using has suddenly included these add-ons. But what has me REALLY incensed is the fact that a means to allow these add-ons in spite of whatever security risk they may pose is not made immediately available for those of us who are willing to accept the risk of using an add-on that hasn't met your entirely arbitrary signing policy. I don't really expect anyone to take any action to solve this problem even though I think you ought to. I hope you will let us know when the pissing contest is over.

所有回覆 (4)

more options

Any particular reason why you are Testing the builds on the Beta channel (currently at first beta 41.0b1) and not the 40.0 Release that came out on Tuesday?. or is it for the Win64 builds in which Fx 41.0 may be the first Release to have Win64.

Firefox 40: Firefox warns about signatures but doesn't enforce them. Firefox 41: Firefox will have a preference that allows signature enforcement to be disabled (xpinstall.signatures.required in about:config). Firefox 42: Release and Beta versions of Firefox 42.0 will not allow unsigned extensions to be installed, with no override.

由 James 於 修改

more options

The Lastpass author has had some updates for this extension. Version 3.2.16.1a Released August 12, 2015 https://addons.mozilla.org/en-US/firefox/addon/lastpass-password-manager/versions/

由 James 於 修改

more options

It beats me James. I'm running Window 7 64bit and this iteration of FF came up as the version supporting 64 bit installs. I suppose you would suggest that I find and download an earlier iteration of FF. I guess that what I will have to do, but it STILL does not answer my question about how come add-ons are OK one day and a security threat the next.

more options

You are testing the Beta builds which has 41.0 current on that channel so you are seeing the changes now and not later.

The current version is Firefox 40.0 from mozilla.org/firefox/all