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.
HTTPS Everywhere Chrome 2016.10.20 corrupted even on Chrome 54+ #7456
We've had at least two reports of the "This extension may have been corrupted" issue on HTTPS Everywhere 2016.10.20, one on Chrome 54.0.2840.71 m (64-bit), and the other on 54.0.2840.59 (64-bit).
Reacted by grub-basket, farmertammy, Brandon Bayer, Adam Pritchard, Matt Blum and Navin Francis Shajan
not working here either with the same error. Win10, Chrome 54.0.2840.71 m (64-bit), HTTPS Everywhere 2016.10.20. Have tried removing and adding from store and eff site as well as multiple repair attempts on each. Tried all the settings for 'Extension Content Verification' (default, enforce(both), and bootstrap) with no success.
I have HTTPS Everywhere currently working on my Mac 10.11.5 with Chrome 54.0.2840.71 (64-bit), but it's not working, even with a Chrome Repair and manual extension re-install, on Windows 10 Pro 64-bit (that's probably behind some security updates) and Chrome 53.0.2785.143 m.
My Chrome on Windows 10 crashed (after who knows how long :) ). Once restarted, is at version 54.0.2840.99 m.
Repaired the HTTPS Everywhere Extension, this time the process looks like it did more by removing, re-downloading, and installing it. Now it appears to work!
HTTPS Everywhere 2016.11.8 corrupted on Chrome 54.0.2840.99 m (64-bit). Repair does not work ; uninstall and then reinstall adds HTTPS E again, but immediately shows it as corrupted -- again - repair does not work on the reinstalled extension. See attached file.
One thing to note: ALL of my other extensions have the option "Allow in incognito" -- HTTPS E does not -- but it was working not too long ago.
HTTPS Everywhere 2016.11.8 corrupted on Chrome 54.0.2840.98 under OS X 10.11.6
"Repair" fails to repair
delete extension, restart Chrome, install extension --> seems to install then status reverts to corrupted.
2016.11.30 corrupted on Chrome 53.0.2785.143, "Repair" failed.
It is of note that this happens whenever the extension updates AFTER I have changed, disabled or added a rule, and the Chrome version does NOT store custom rules or rule changes in the expected files as the Firefox version does. If I change no settings, the extension does not become corrupt.
I believe the Chrome version is improperly storing rule changes, leading to corruption being detected when the extension updates and Chrome re-verifies it.
@zardozman The custom rules of HTTPS-EW for Chrome are stored in LocalStorage because Chrome doesn't allow changes in files.
Also could you check C:\Users\{Username}\AppData\Local\Google\Chrome\User Data\Default\Extensions\gcbommkclmclpchllfjekcdonpmejbdp\2016.11.8_0\_metadata?
@Hainish Thanks for the pointer. I will post there if I can repro again. I had a consistent, 100% repro until I tried with net-internals running... and now it works fine.
A comment has been made in the Chromium bugtracker. A lot of the corruption errors are showing up due to server-side throttling on their end. This problem should be fixed (or at least alleviated) later this week.
FYI: I decided to change my default browser from Firefox to Chrome, then I installed HTTPS Everywhere on Chrome, everything was working fine, then I did a new Profile, to start fresh. I needed to re-installed HTTPS... in the new profile. Now on the new profile I have the problem that the extension is maybe corrupted and I cannot make it work at all, while it's still working fine on the other. I'm running Chrome 56.0.2924.87.
To paraphrase the problem described in the Chromium bugtracker that @Hainish linked earlier: EFF extensions like HTTPS Everywhere and Privacy Badger are sort of unique because they don't entirely trust Google's signing process, so there are extra steps involved when a user installs or updates the extension. One of these extra steps is that the user's browser requests extra verification information from Google. The bugtracker issue is that Google doesn't always handle these requests properly, and when they don't, the user gets the corrupted extension error. That's why it sometimes happens and sometimes doesn't. Google's intended fix is to handle these extra verification requests better on their end, hopefully by later this week.
@Hainish, please correct me if this is too inaccurate.
@asmosn please open a new issue. Screenshots are appreciated as well as any additional info you can provide (platform, is it a new profile, your extension version, etc).
Activity
farmertammy commentedon Nov 1, 2016
not working here either with the same error. Win10, Chrome 54.0.2840.71 m (64-bit), HTTPS Everywhere 2016.10.20. Have tried removing and adding from store and eff site as well as multiple repair attempts on each. Tried all the settings for 'Extension Content Verification' (default, enforce(both), and bootstrap) with no success.
gloomy-ghost commentedon Nov 3, 2016
It would be great if you could provide some details, or report to here straightly since it's not https everywhere's fault.
Pysis868 commentedon Nov 10, 2016
I have HTTPS Everywhere currently working on my Mac 10.11.5 with Chrome 54.0.2840.71 (64-bit), but it's not working, even with a Chrome Repair and manual extension re-install, on Windows 10 Pro 64-bit (that's probably behind some security updates) and Chrome 53.0.2785.143 m.
gloomy-ghost commentedon Nov 10, 2016
@Pysis868 For the case on Windows, please try to upgrade to Chrome 54 first
yochananmarqos commentedon Nov 11, 2016
The extension works fine on Chrome 54 stable, but it shows corrupted on 55 beta.
HTTPS Everywhere 2016.11.8
Chrome 55.0.2883.44 beta (64-bit)
Linux Mint 18 Sarah Cinnamon Edition
hao19 commentedon Nov 11, 2016
Getting the extension corrupted error on chrome 54 (64-bit), windows 7 SP1 clean install
Pysis868 commentedon Nov 16, 2016
My Chrome on Windows 10 crashed (after who knows how long :) ). Once restarted, is at version 54.0.2840.99 m.
Repaired the HTTPS Everywhere Extension, this time the process looks like it did more by removing, re-downloading, and installing it. Now it appears to work!
kontinuity commentedon Nov 16, 2016
The extension has this issue with Mac 10.12.1 and Chrome Version 54.0.2840.98 (64-bit)
fb9d668f commentedon Nov 17, 2016
HTTPS Everywhere 2016.11.8 corrupted on Chrome 54.0.2840.99 m (64-bit). Repair does not work ; uninstall and then reinstall adds HTTPS E again, but immediately shows it as corrupted -- again - repair does not work on the reinstalled extension. See attached file.
One thing to note: ALL of my other extensions have the option "Allow in incognito" -- HTTPS E does not -- but it was working not too long ago.
tthrift commentedon Nov 28, 2016
HTTPS Everywhere 2016.11.8 corrupted on Chrome 54.0.2840.98 under OS X 10.11.6
"Repair" fails to repair
delete extension, restart Chrome, install extension --> seems to install then status reverts to corrupted.
zardozman commentedon Dec 1, 2016
2016.11.30 corrupted on Chrome 53.0.2785.143, "Repair" failed.
It is of note that this happens whenever the extension updates AFTER I have changed, disabled or added a rule, and the Chrome version does NOT store custom rules or rule changes in the expected files as the Firefox version does. If I change no settings, the extension does not become corrupt.
I believe the Chrome version is improperly storing rule changes, leading to corruption being detected when the extension updates and Chrome re-verifies it.
gloomy-ghost commentedon Dec 1, 2016
@zardozman The custom rules of HTTPS-EW for Chrome are stored in LocalStorage because Chrome doesn't allow changes in files.
Also could you check
C:\Users\{Username}\AppData\Local\Google\Chrome\User Data\Default\Extensions\gcbommkclmclpchllfjekcdonpmejbdp\2016.11.8_0\_metadata?gloomy-ghost commentedon Dec 1, 2016
@Hainish HTTPS Everywhere got corrupted on my Chrome (54, on Win10) after 11.30 release, and
_metadatadoesn't exist... Repairing helps.hao19 commentedon Dec 2, 2016
This issue seems to be fixed in the latest Chrome 55 release.
fb9d668f commentedon Dec 2, 2016
15 remaining items
ek68794998 commentedon Feb 15, 2017
Still seeing this issue on 2017.2.13. (Chrome 56.0.2924.87)
Hainish commentedon Feb 16, 2017
@ekumlin please comment here with as much info as possible regarding your configuration and versioning.
ek68794998 commentedon Feb 16, 2017
@Hainish Thanks for the pointer. I will post there if I can repro again. I had a consistent, 100% repro until I tried with
net-internalsrunning... and now it works fine.Hainish commentedon Feb 21, 2017
A comment has been made in the Chromium bugtracker. A lot of the corruption errors are showing up due to server-side throttling on their end. This problem should be fixed (or at least alleviated) later this week.
dotzerosec commentedon Feb 23, 2017
FYI: I decided to change my default browser from Firefox to Chrome, then I installed HTTPS Everywhere on Chrome, everything was working fine, then I did a new Profile, to start fresh. I needed to re-installed HTTPS... in the new profile. Now on the new profile I have the problem that the extension is maybe corrupted and I cannot make it work at all, while it's still working fine on the other. I'm running Chrome 56.0.2924.87.
jeremyn commentedon Feb 23, 2017
To paraphrase the problem described in the Chromium bugtracker that @Hainish linked earlier: EFF extensions like HTTPS Everywhere and Privacy Badger are sort of unique because they don't entirely trust Google's signing process, so there are extra steps involved when a user installs or updates the extension. One of these extra steps is that the user's browser requests extra verification information from Google. The bugtracker issue is that Google doesn't always handle these requests properly, and when they don't, the user gets the corrupted extension error. That's why it sometimes happens and sometimes doesn't. Google's intended fix is to handle these extra verification requests better on their end, hopefully by later this week.
@Hainish, please correct me if this is too inaccurate.
dotzerosec commentedon Feb 23, 2017
That make sense, because now, for no apparent reason (well for the problem you just explain), the extension is working well.
chanan commentedon Feb 23, 2017
I would suggest updating the FAQ section of the website and/or putting a note on the home page till this is resolved by Google.
Hainish commentedon Apr 8, 2017
Haven't been getting reports to this effect lately. Closing this until I get further reports.
asmosn commentedon Jul 18, 2017
the same problem still exist on 59.0.3071.115[stable] and 61.0.3153.0 [dev].
and it is getting more serious !
Hainish commentedon Jul 18, 2017
@asmosn please open a new issue. Screenshots are appreciated as well as any additional info you can provide (platform, is it a new profile, your extension version, etc).
leonhu0710 commentedon Dec 14, 2017
the same problem still exist on 63.0.3239.84[stable] [64 bit].Occured about 20 times thus far.
jeremyn commentedon Dec 14, 2017
@leonhu0710 Please open a new issue with the information requested by @Hainish in his previous comment.
leonhu0710 commentedon Dec 15, 2017
@jgillula okey.