You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Extension is broken/corrupted and won't repair on Chrome #5874
I see the problem both on Mac OS 10.11.6 with Chrome 54.0.2810.2 and on Ubuntu 14.04. The fact that it "broke" and I didn't notice it immediately seems like comp.risks fodder.
Reacted by qinwf, Andrew Meyer, Dominyk Tiller, ourichermath, Jacob Bearden, Rudi, Kay S. Thiele, Simon Cropp, Charles Qiu, Gerard Chin and 12 more
I can reproduce this, looks like it's fairly platform-independent, happening with Chrome 54 across the board. @semenko any idea what may be going on here?
Hm, IIRC that failure results when a local checksum/signature of the extension contents doesn't match the signature of what was submitted to the Chrome app store. (The intent is to prevent malware from modifying extension scripts.)
I've yet to see this personally -- and I don't have a great idea of what could be causing it.
If this weren't platform independent, I'd guess some client-side antivirus was rewriting / removing some of our package data [e.g. for a "suspicious" url].
Thanks @semenko. Looks like this is happening with our Privacy Badger extension on Chrome 54 as well. This may be some extra contents that are packaged but not checked on either the client-side or Chrome Web Store side. I'll have to consider how to debug this, though - seems tricky, and I don't see any debugging output. I wonder if we have contacts at CWS that can help?
If this issue is disappearing from a point upgrade, as reported above, they may well know about it and have fixed it already. I wouldn't count on it, though - I still see it for the latest Linux Chrome dev 54.0.2824.0. I'm with @semenko and @cooperq on this, probably best to find someone on the Chrome side to help us debug this.
I'm posting my info in the other thread #7456 that is more recent and may more closely apply to the cause for my problem than this one, if that is fine.
Still experiencing this issue on Chrome 55 (64bit) / Ubuntu 16. Privacy Badger fails to work properly either, both "corrupt" immediately after installation.
Activity
auyongcheemeng commentedon Aug 1, 2016
Ditto on the the problem on Chrome 54.0.2810.2 (64 bit) on Win10.
Hainish commentedon Aug 8, 2016
I can reproduce this, looks like it's fairly platform-independent, happening with Chrome 54 across the board. @semenko any idea what may be going on here?
semenko commentedon Aug 8, 2016
Hm, IIRC that failure results when a local checksum/signature of the extension contents doesn't match the signature of what was submitted to the Chrome app store. (The intent is to prevent malware from modifying extension scripts.)
I've yet to see this personally -- and I don't have a great idea of what could be causing it.
If this weren't platform independent, I'd guess some client-side antivirus was rewriting / removing some of our package data [e.g. for a "suspicious" url].
Hainish commentedon Aug 8, 2016
Thanks @semenko. Looks like this is happening with our Privacy Badger extension on Chrome 54 as well. This may be some extra contents that are packaged but not checked on either the client-side or Chrome Web Store side. I'll have to consider how to debug this, though - seems tricky, and I don't see any debugging output. I wonder if we have contacts at CWS that can help?
semenko commentedon Aug 9, 2016
Very odd -- maybe there's a strange character encoding / odd file making it's way in, and that's hitting an edge case in Chrome?
I don't see this in 54.0.2816.0 (Ubuntu). And I don't see any similar bugs at https://crbug.com/
Hainish commentedon Aug 9, 2016
cc @cooperq - is there a similar issue for Privacy Badger you can link to?
faried commentedon Aug 9, 2016
I'm not sure what caused it, but it seems fixed now. Maybe a transient issue with Chrome dev? I'm on 54.0.2816.4 on OS X and 54.0.2816.0 on Linux now.
I ran into the Privacy Badger issue on Linux at the same time, but not on OS X.
Hainish commentedon Aug 9, 2016
@faried I'm still seeing it on Ubuntu w/ Chrome 54.0.2816.0 (64-bit)
Hainish commentedon Aug 10, 2016
In 54.0.2824.0 dev-m (64-bit) on Windows 10, HTTPSE successfully installs.
I'm still getting a failure to install for 54.0.2824.0 dev (64-bit) on Ubuntu.
cooperq commentedon Aug 11, 2016
Relevant privacy badger issue: EFForg/privacybadger#843
semenko commentedon Aug 11, 2016
My instinct is that this is an edge case / error with the custom key/signing process, which isn't used very commonly with extensions.
(the 'key' parameter in manifest.json / https://developer.chrome.com/extensions/packaging )
cooperq commentedon Aug 11, 2016
@semenko this is my instinct as well. I suspect we should talk to someone at google about this.
Hainish commentedon Aug 11, 2016
If this issue is disappearing from a point upgrade, as reported above, they may well know about it and have fixed it already. I wouldn't count on it, though - I still see it for the latest Linux Chrome dev 54.0.2824.0. I'm with @semenko and @cooperq on this, probably best to find someone on the Chrome side to help us debug this.
cooperq commentedon Aug 11, 2016
For me it has been around for a while, so I doubt it will go away on a point upgrade.
112 remaining items
gloomy-ghost commentedon Oct 29, 2016
There is another report: #7456
Pysis868 commentedon Nov 10, 2016
Just had the issue today (11/10/2016). Will check this new thread in #7456 in case it is a different root cause.
Hainish commentedon Nov 10, 2016
@Pysis868 what version of the extension are you using?
On November 10, 2016 11:37:24 AM PST, Pysis868 notifications@github.com wrote:
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Pysis868 commentedon Nov 10, 2016
I'm posting my info in the other thread #7456 that is more recent and may more closely apply to the cause for my problem than this one, if that is fine.
mezmi commentedon Dec 13, 2016
Still experiencing this issue on Chrome 55 (64bit) / Ubuntu 16. Privacy Badger fails to work properly either, both "corrupt" immediately after installation.
Swimmer63 commentedon Dec 13, 2016
Same here. This is a problem as of today.
StoneLegion commentedon Jan 17, 2017
Same issue here. Version 55.0.2883.87 m
StoneLegion commentedon Jan 17, 2017
@Hainish Please reopen.
Hainish commentedon Jan 17, 2017
@KaneHart this issue is tracking current "extension corrupted" reports: #7456
dglezschez commentedon Jan 24, 2017
Updated Chrome today, still having the issue with HTTPSE
Neither option given here (reinstall, restart, enable, Repair...) works. Windows 7 32bit
iainbryden commentedon Jan 26, 2017
I also have "extension may be corrupted" errors. Two laptops, Windows 7, Chrome, version 2016.12.19
Hainish commentedon Jan 26, 2017
This issue is tracking current "extension corrupted" reports: #7456. Please issue reports there. Locking conversation.