Closed
Bug 1043017
Opened 11 years ago
Closed 10 years ago
Blocklist enformation add-on
Categories
(Toolkit :: Blocklist Policy Requests, defect)
Toolkit
Blocklist Policy Requests
Tracking
()
RESOLVED
FIXED
2014-08
People
(Reporter: kmag, Assigned: jorgev)
References
Details
(Whiteboard: [qa-])
Crossrider add-on silently installed by WinAmp installer on c|net. Users currently only number in the hundreds, but are all silent installs.
f6682b47-e12f-400b-9bc0-43b3ccae69d1@39d6f481-b198-4349-9ebe-9a93a86f9267.com
Comment 1•11 years ago
|
||
Hello Kris,
We had been notified of this thread through bugzilla subscription and had blocked this extension on our end as well and removed all existing code.
On top of this we had contacted the developer after the block and had warned him that if we will see this again we will ban him completely from our platform.
Shmueli - Crossrider
Assignee | ||
Comment 2•10 years ago
|
||
Does that mean that it is safe to blocklist that ID since the add-on doesn't do anything anymore?
Flags: needinfo?(shmueli)
Reporter | ||
Comment 3•10 years ago
|
||
I've tested this add-on, I'm not satisfied that this add-on has been blocked per the mechanism that we discussed.
Regardless, I don't think that it's appropriate to rely on third-party blocking mechanisms in cases like this. It might be acceptable large-scale, to avoid a blanket block of this ID pattern, but in specific cases like this, we should use our normal blocklisting process.
Assignee | ||
Comment 4•10 years ago
|
||
I agree. If Crossrider's policy is to block these add-ons right away, I don't see why it shouldn't be ours as well. I find it confusing that users will end up with a non-functional entry, and it's unclear to me if any of this is communicated to them.
Blocked: https://addons.mozilla.org/en-US/firefox/blocked/i682
Assignee: nobody → jorge
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(shmueli)
Resolution: --- → FIXED
Whiteboard: [qa-]
Target Milestone: --- → 2014-08
Updated•9 years ago
|
Product: addons.mozilla.org → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•