Closed Bug 863387 Opened 11 years ago Closed 11 years ago

Blocklist Default Tab add-on

Categories

(Toolkit :: Blocklist Policy Requests, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

VERIFIED FIXED
2013-06-13

People

(Reporter: kmag, Assigned: jorgev)

References

()

Details

+++ This bug was initially created as a clone of Bug #863385 +++

Adds a new search box to the end of the tab bar (fortunately does not hide the builtin one in the process), changes the new tab page to a crappy search page.

The first time I uninstall it and then restart, it's back, but without the Remove button. I can then disable it. I suppose that means they're installing it once globally and once in the profile.

It also does not restore autoDisableScopes after being installed. In fact, the default value remains set at 0, seemingly because the following have been added to my profile's defaults/preferences/prefs.js file:

pref("extensions.autoDisableScopes", 0);
defaultPref("extensions.autoDisableScopes", 0);
lockPref("extensions.autoDisableScopes", 0);

ID: addon@defaulttab.com
Also, this ID has an AMO listing: https://addons.mozilla.org/addon/default-tab-recovery/
Summary: Blocklist RapidFinda add-on → Blocklist New Tab add-on
Summary: Blocklist New Tab add-on → Blocklist Default Tab add-on
Sorry, it looks like it was a PC Backup installer deceptively linked from the top left of that page that I installed, rather than Fun4IM.
(In reply to Kris Maglione [:kmag] from comment #1)
> Also, this ID has an AMO listing:
> https://addons.mozilla.org/addon/default-tab-recovery/

Mike, IIRC, you were the one who asked us to keep that AMO listing. Can you let us know if that ID still has any valid use, or if it is safe to block?
Jorge - This is Steve Wise Search Results, the Default Tab addon is ours. We are not making any changes to the scopes during install as Chris mentions above, and on uninstall we are completely removed.  Let me know how we can resolve the issue.

Thanks,
Steve
Also, the http://fun4im.software.informer.com/ is not associated with the Default Tab product.
so looking at bug 863385, I'm unclear as to which behaviors you attribute to that obviously malicious addon versus default tab. 

did default tab have the uninstall problem or did the other add-on have the problem? 

I'm trying to figure out what specific behavior would cause Default Tab to be block listed.
OK, I've looked into the installer Default Tab is using. It does not modify any Firefox preference files and it doesn't add anything to the Windows registry.
Kris, can you locate the installer that is silently dropping Default Tab in the profile?
Flags: needinfo?(kmaglione+bmo)
We are building a new installer and will have it in production in the next day or so to resolve the issue. I will follow up when it is done.
I can't. The original installer that I found apparently came from an ad which is not there anymore.

mkaply, do you know where this is normally distributed?
Flags: needinfo?(kmaglione+bmo) → needinfo?(mozilla)
It's distributing via things like w3i or other third party installers.
Flags: needinfo?(mozilla)
Do you know of any specific installers I can download to test?
The installer they sent me does not have any of the above issues. Assuming that the other installers are likewise fixed, we should only block older versions of the add-on.
Which version does the new installer include?
2.0, but I'm not sure what version the old installer included.
The old installer could have been anything from 1.4.4 and down.

We went to 2.0 to make it easy to distinguish the new from the old.
Versions 0 - 1.4.4 have been blocked.

https://addons.mozilla.org/en-US/firefox/blocked/i362
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
they have reacted with a 2.0 version of this addon.
THIS IS NOT FIXED
https://support.mozilla.org/en-US/questions/956466
kdurant,

I don't think you understand what happened here. The issue was not with the functionality of the add-on, it was with the install method.

The company that makes Default Tab has modified their install method so that version 2.0 installs the correct way.

So any version under 2.0 has been blacklisted, but versions above have not been because they do the right thing.

As far as this support.mozilla.org issue goes, if the add-on was installed, it would have been via a third party installer which was opted in as part of an install.
OH that is alright.
Assignee: nobody → jorge
Target Milestone: --- → 2013-06-13
Verified as fixed . Older versions are blocklisted.
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → Toolkit
You need to log in before you can comment on or make changes to this bug.