Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
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

Closed

Description

@jgillula

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).

Activity

  1. farmertammy commented on Nov 1, 2016

    @farmertammy

    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.

  2. gloomy-ghost commented on Nov 3, 2016

    @gloomy-ghost
    Collaborator

    It would be great if you could provide some details, or report to here straightly since it's not https everywhere's fault.

  3. Pysis868 commented on Nov 10, 2016

    @Pysis868

    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.

  4. gloomy-ghost commented on Nov 10, 2016

    @gloomy-ghost
    Collaborator

    @Pysis868 For the case on Windows, please try to upgrade to Chrome 54 first

  5. yochananmarqos commented on Nov 11, 2016

    @yochananmarqos

    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

  6. hao19 commented on Nov 11, 2016

    @hao19

    Getting the extension corrupted error on chrome 54 (64-bit), windows 7 SP1 clean install

  7. Pysis868 commented on Nov 16, 2016

    @Pysis868

    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!

  8. kontinuity commented on Nov 16, 2016

    @kontinuity

    The extension has this issue with Mac 10.12.1 and Chrome Version 54.0.2840.98 (64-bit)

  9. fb9d668f commented on Nov 17, 2016

    @fb9d668f

    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 corrupted_111716

  10. tthrift commented on Nov 28, 2016

    @tthrift

    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.

  11. zardozman commented on Dec 1, 2016

    @zardozman

    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.

  12. gloomy-ghost commented on Dec 1, 2016

    @gloomy-ghost
    Collaborator

    @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?

  13. gloomy-ghost commented on Dec 1, 2016

    @gloomy-ghost
    Collaborator

    @Hainish HTTPS Everywhere got corrupted on my Chrome (54, on Win10) after 11.30 release, and _metadata doesn't exist... Repairing helps.

  14. hao19 commented on Dec 2, 2016

    @hao19

    This issue seems to be fixed in the latest Chrome 55 release.

  15. fb9d668f commented on Dec 2, 2016

    @fb9d668f
  16. 15 remaining items

  17. ek68794998 commented on Feb 15, 2017

    @ek68794998

    Still seeing this issue on 2017.2.13. (Chrome 56.0.2924.87)

    The extension may have been corrupted.

  18. Hainish commented on Feb 16, 2017

    @Hainish
    Member

    @ekumlin please comment here with as much info as possible regarding your configuration and versioning.

  19. ek68794998 commented on Feb 16, 2017

    @ek68794998

    @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.

  20. Hainish commented on Feb 21, 2017

    @Hainish
    Member

    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.

  21. dotzerosec commented on Feb 23, 2017

    @dotzerosec

    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.

  22. jeremyn commented on Feb 23, 2017

    @jeremyn
    Contributor

    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.

  23. dotzerosec commented on Feb 23, 2017

    @dotzerosec

    That make sense, because now, for no apparent reason (well for the problem you just explain), the extension is working well.

  24. chanan commented on Feb 23, 2017

    @chanan

    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.

  25. Hainish commented on Apr 8, 2017

    @Hainish
    Member

    Haven't been getting reports to this effect lately. Closing this until I get further reports.

  26. asmosn commented on Jul 18, 2017

    @asmosn

    the same problem still exist on 59.0.3071.115[stable] and 61.0.3153.0 [dev].
    and it is getting more serious !

  27. Hainish commented on Jul 18, 2017

    @Hainish
    Member

    @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).

  28. leonhu0710 commented on Dec 14, 2017

    @leonhu0710

    the same problem still exist on 63.0.3239.84[stable] [64 bit].Occured about 20 times thus far.

  29. jeremyn commented on Dec 14, 2017

    @jeremyn
    Contributor

    @leonhu0710 Please open a new issue with the information requested by @Hainish in his previous comment.

  30. leonhu0710 commented on Dec 15, 2017

    @leonhu0710

    @jgillula okey.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions