Extension incorrectly shows up as blacklisted in chrome://extensions page |
||||
Issue descriptionhttps://twitter.com/lslez/status/793849311263989760 shows a screenshot of this extension: https://chrome.google.com/webstore/detail/tabby-cat/mefhakmgclhhfbdadeojlkbllmecialg being marked as "this extension contains malware". One unexpected thing is that the page also shows it as being Enabled - from a quick look at the code, when this error message (IDS_OPTIONS_BLACKLISTED_MALWARE) is displayed, the blacklisted state of the extension should be extensions::BlacklistState ::BLACKLISTED_MALWARE and it should be forcibly disabled with no option to re-enable it, just to uninstall it. We did have a fix to a problem with handling blacklist state a little while back: https://codereview.chromium.org/2147923002/ But that should have gone out in M54, which presumably most users should be running by now. I'm going to reach out to the developer to confirm a few things: -The id in the install where this happens is actually "mefhakmgclhhfbdadeojlkbllmecialg" -The running chrome version is 54 or higher -Safe Browsing is turned on and ask for more information.
,
Nov 4 2016
,
Apr 12 2017
Hello! I'm the developer. I was finally able to confirm these points with a user that is still experiencing this bug: - The id is "mefhakmgclhhfbdadeojlkbllmecialg" - The Chrome version was 56.0.2924.87 - Safe Browsing was turned on Please let me know how else I can help! I'm asking for the extension logs and I'll send them over to Antony.
,
Apr 17 2017
Seems like this might be a problem with our malware detection pipeline then. I'm assigning the issue to jawag@ for follow-up since I'm no longer working on chrome.
,
Apr 17 2017
ackermanb@, can you confirm that there's no reason from a SB point of view this should be happening? lesliezacharkow@, to confirm, you can't reproduce this at all, right? Just user reports? (Asking because it'd be helpful to take a look at the preferences chrome has listed for the extension.)
,
Apr 17 2017
This should not be happening, the extension is not on our blacklist.
,
Aug 24 2017
Any updates here? Chrome Web Store Dev Support recently got another report of this happening.
,
Aug 24 2017
I think we need a bit more to go on to really find out what's going on here. In particular, it'd be useful to see what the preference entries for that extension look like. There are a lot of hypothetical failure points, but it's difficult to know which one is causing this without more information - and some are quite outside of our control (like pref corruption, either intentional or not). |
||||
►
Sign in to add a comment |
||||
Comment 1 Deleted