Closed
Bug 601937
Opened 14 years ago
Closed 13 years ago
Noscript was uninstalled/reinstall with the last FF major update
Categories
(Firefox :: Security, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 680802
People
(Reporter: skibo1219, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729; .NET4.0C)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729; .NET4.0C)
Basically as the summary says. Noscript is a crucial add-on for the security of my computer with the last update to Firefox. There are also a couple other add-on/plug-ins, etc. that were uninstalled or removed forthe update. if this was intentional then a major warning label should have accompanied the update.
Reproducible: Didn't try
Its a pain the ass to hunt down previously install add-ins to see if they have been updated with the new updated Firefox core. thanks for the headache
Comment 1•14 years ago
|
||
This doesn't appear to be an exploitable security problem, un-hiding the bug so more people can help out.
What did you update from? Were you on the previous 3.6.9 release or an older 3.5.x or 3.0.x one?
Generally what is supposed to happen when you update using the built-in updater is that we check before you upgrade, and if the upgrade will make some of your add-ons incompatible the update prompt will tell you that and list those add-ons. If you weren't on a compatible version, but a compatible version is available it will let you know. And if you upgrade anyway the add-ons are NOT removed they are merely disabled, so that when a compatible version is available you can easily update to it.
This is especially strange because NoScript is perfectly compatible with 3.6.10 -- I'm using it as I type this.
If your add-ons are just plain gone I wonder if somehow you ended up with a parallel install or a new profile shadowing the one you use. Are your bookmarks and browsing history also missing? There are a couple of potential causes of this, for example a plugin didn't let the browser shut down completely during the upgrade, so it couldn't use the same profile. I thought we fixed the causes we knew about but the support folks would know more. You will also find help on getting your profile back (if that is in fact the problem) at our support site. Please ask for help at http://support.mozilla.com/ (or look for the existing help page on this topic and follow the recovery steps).
Group: core-security
What did you update from? Were you on the previous 3.6.9 release or an older
3.5.x or 3.0.x one?
I have install the update as they are released, settings are set to check every time I open FF, so this happened between the current release and the previous one. i am currently on 3.6.10, and Noscript was the only app affected (so far) The fix was to find and re-install the app. Noscript is better protection then any AV program can offer within a browser, Im glad its not exploitable, but it still deserves attention. (my profile is fine)
Updated•13 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•