Closed
Bug 1340811
Opened 8 years ago
Closed 8 years ago
[Policy Violation] TrackMeNot resets default search engine
Categories
(addons.mozilla.org :: Security, defect)
addons.mozilla.org
Security
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: cliff_bugzilla, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170125094131
Steps to reproduce:
The TrackMeNot add-on keeps setting my default search engine to Yahoo. To prove this, I deleted my Firefox installation (on the Mac, this includes the <user>/Library/Application Support/Firefox folder). Then I re-installed it, and added my add-ons back one by one. After adding TrackMeNot, the behavior returned.
Actual results:
It resets the default search engine to Yahoo at periodic intervals - it seems to be about an hour, but the precise interval is not clear.
Expected results:
It should respect my default search engine setting and not change it. I believe this is a violation of add-on policy.
Reporter | ||
Updated•8 years ago
|
Group: firefox-core-security
Component: Add-ons → Tracking Protection
Keywords: sec-high
Product: Tech Evangelism → Firefox
Version: Firefox 51 → 51 Branch
Comment 1•8 years ago
|
||
The add-on in question is probably https://addons.mozilla.org/en-US/firefox/addon/trackmenot/
What's worse, there are already reports in the reviews that also tell us they are messing with the search settings,
e.g. https://addons.mozilla.org/en-US/firefox/addon/trackmenot/?src=search
Group: firefox-core-security, core-security
Component: Tracking Protection → Security
Product: Firefox → addons.mozilla.org
Summary: TrackMeNot resets default search engine → [Policy Violation] TrackMeNot resets default search engine
Version: 51 Branch → unspecified
Comment 2•8 years ago
|
||
The whole point of that addon it that it randomizes the search engine periodically. Given that, I think this bug is invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•