Kaspersky Internet Security for Windows extension is not added to Firefox during installation
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
People
(Reporter: asoncutean, Unassigned)
References
Details
Affected versions
- 77.0.1
- 78.0b6
- 79.0a1
Affected platforms
- Windows 10
Steps to reproduce
- Install Firefox
- Install Kaspersky Internet Security for Windows
Expected result
- A doorhanger to enable the antivirus addon is available
Actual result
- No Kaspersky addon is added to Firefox
Regression range
- Encountered during testing for beta 78, I will come back with additional information.
Additional notes
- The “Kaspersky Protection” extension is added in Chrome
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 1•4 years ago
|
||
I’ve tried to determine if this issue is a regression. I can reproduce it on my machine with every build I’ve tested (Nightly, Beta, Release) way back to builds from 2016 (for Beta) and 2014 (for Nightly).
Comment 2•4 years ago
|
||
The severity field is not set for this bug.
:mixedpuppy, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 3•4 years ago
|
||
Are there any errors in the console? Does the addon appear anywhere in about:addons? I'm not really interested in installing kaspersky on my machine, so we will need to get some kind of data here.
Reporter | ||
Comment 4•4 years ago
|
||
(In reply to Shane Caraveo (:mixedpuppy) from comment #3)
Are there any errors in the console? Does the addon appear anywhere in about:addons?
- I have Firefox (clean profile) and Chrome opened while installing the antivirus, the add-on is added to Chrome, nothing happens on Firefox, no error can be seen inside the console; but after I restart the browser I ended up with the following error
- No, the addon is not inside the about:addons page.
Comment 5•4 years ago
|
||
Does the extension show up in about:support?
This essentially sounds like Kapersky is attempting to sideload the extension from a location we no longer support sideloading in. Can you also test with the latest ESR (which does still support sideloading) ?
Reporter | ||
Comment 6•4 years ago
|
||
(In reply to Shane Caraveo (:mixedpuppy) from comment #5)
Does the extension show up in about:support?
This essentially sounds like Kapersky is attempting to sideload the extension from a location we no longer support sideloading in. Can you also test with the latest ESR (which does still support sideloading) ?
- Still no addon on the latest Esr build: screenshot Firefox vs Chrome and the about:support content
Updated•4 years ago
|
Comment 7•4 years ago
|
||
Can you attach extensions.json and addonStartup.json.lz4?
Reporter | ||
Comment 8•4 years ago
|
||
(In reply to Shane Caraveo (:mixedpuppy) (on PTO) from comment #7)
Can you attach extensions.json and addonStartup.json.lz4?
Updated•4 years ago
|
Comment 9•4 years ago
•
|
||
Hello, encountered this with McAfee Total Protection (16.0 R25) and Firefox 81.0b7 under Windows 7. There was no addon installed in Firefox, and reinstalling both the AV software and Firefox didn't help.
Comment 10•4 years ago
|
||
When I install Kaspersky, it prompts me for protecting firefox, has me restart it, and sends me to AMO to install the kaspersky addon. From that, I'm not clear that Kaspersky is installing an addon when the main software is installed or not. Do you know for certain that it is supposed to install an addon?
McAfee doesn't seem to have a free trial, is QA able to test with that (and verify whether it is supposed to install an addon)?
Reporter | ||
Comment 11•4 years ago
|
||
(In reply to Shane Caraveo (:mixedpuppy) from comment #10)
Do you know for certain that it is supposed to install an addon?
That is a good point, I am not sure what I’ve written as the expected result, is really the expected one at this moment. Initially, when we first started to target specific AV test cases, add-ons were set as default. After a brief discussion with my colleague, who was in charge of this part, the conclusion is still not a certain one, some gdpr policy implication could have changed the way that add-ons are handled now. Do you have any insights on this matter, it is maybe the case to reach the AV companies separately for a clear answer? As a side note, I don't have a test machine at my disposal this week to accommodate AV testing. If needed for any further question, I think I should be able to accommodate any request on the next one.
Comment 12•4 years ago
|
||
I've verified with Kaspersky that they no longer sideload extensions.
Description
•