Closed Bug 410315 Opened 17 years ago Closed 8 years ago

McAfee SiteAdvisor can conflict with other extensions

Categories

(Plugins Graveyard :: McAfee AV, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: kohei, Unassigned)

References

Details

McAfee SiteAdvisor has been conflicting with a lot of extensions:

* Minimize To Tray Enhancer
* Fast Video Download
* Irvine ContextMenu
* Internote
* ThumbStrips
* 1-ClickWeather
* Autocomplete Manager
* WOT
* Operator
* Make Link
* Translation Panel

I heard that the cause (of at least some of them) was an extra function Array.prototype.inArray added by the SiteAdvisor. The source is loaded from remote site:
https://sadownload.mcafee.com/products/sa/firefox/search.dat
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
I think this is a different problem from Bug 404122. Please read my description, not only summary.
Feel free to mention it in bug 404122 where we are already planning to do outreach to McAfee for issues. As it stands merely conflicting with other extensions is not grounds for being added to the blocklist.
http://www.google.com/search?q=siteadvisor+site:addons.mozilla.org
http://www.google.com/search?q=firefox+siteadvisor+conflict

The authors and users of over a dozen extensions have been affected by the troublesome extension. Some users have reported the problem to McAfee but the fixed version has not been available so far.

Anyway, this is completely different from Bug 404122 that for Trunk/Fx3.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
We should reach out to McAfee and get whatever is wrong fixed as with bug 404122
Summary: Add McAfee SiteAdvisor to the extension blacklist → McAfee SiteAdvisor can conflict with other extensions
window, any contacts a mcafee?
I think Mark has been in contact with them.  I think their inArray method can be replaced by Array.prototype.indexOf, which is already built into FF2 and FF3.

I don't see any prototype mutation at
https://sadownload.mcafee.com/products/sa/firefox/search.dat -- has this been fixed, or is that not the right location?

The Array prototype mutation is in a JS file downloaded by the extension, not in the extension itself.

I did trade email with a McAfee contact about the issue.
I forgot to attach a snapshot of search.dat but Array.prototype.inArray in the file was gone. Fixed?
Here's the code snippet from original code:
http://forums.mozillazine.jp/viewtopic.php?p=17452#17452
Any updates on this bug?  We're still seeing compatibility problems for users in Japan.
The blog comments we're seeing are due to Trend Micro Internet Security (ウイルスバスター in Japan.) The SiteAdvisor problem should be fixed now.
Status: REOPENED → RESOLVED
Closed: 17 years ago16 years ago
Resolution: --- → WORKSFORME
We're now tracking such bugs. This doesn't mean it's something we can fix, merely something we hope to be able to point vendors to so they can investigate. This is an automated message.
Status: RESOLVED → UNCONFIRMED
Component: Extension Compatibility → McAfee AV
Ever confirmed: false
Product: Firefox → Plugins
QA Contact: extension.compatibility → mcafee-antivirus
Resolution: WORKSFORME → ---
Version: 2.0 Branch → unspecified
Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago8 years ago
Resolution: --- → INCOMPLETE
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.