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.

Extension is broken/corrupted and won't repair on Chrome #5874

Closed

Description

@faried

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.

screen shot 2016-07-30 at 10 36 23

Activity

  1. auyongcheemeng commented on Aug 1, 2016

    @auyongcheemeng

    Ditto on the the problem on Chrome 54.0.2810.2 (64 bit) on Win10.

  2. Hainish commented on Aug 8, 2016

    @Hainish
    Member

    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?

  3. semenko commented on Aug 8, 2016

    @semenko
    Contributor

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

  4. Hainish commented on Aug 8, 2016

    @Hainish
    Member

    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?

  5. semenko commented on Aug 9, 2016

    @semenko
    Contributor

    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/

  6. Hainish commented on Aug 9, 2016

    @Hainish
    Member

    cc @cooperq - is there a similar issue for Privacy Badger you can link to?

  7. faried commented on Aug 9, 2016

    @faried
    Author

    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.

  8. Hainish commented on Aug 9, 2016

    @Hainish
    Member

    @faried I'm still seeing it on Ubuntu w/ Chrome 54.0.2816.0 (64-bit)

  9. Hainish commented on Aug 10, 2016

    @Hainish
    Member

    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.

  10. cooperq commented on Aug 11, 2016

    @cooperq
    Contributor

    Relevant privacy badger issue: EFForg/privacybadger#843

  11. semenko commented on Aug 11, 2016

    @semenko
    Contributor

    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 )

  12. cooperq commented on Aug 11, 2016

    @cooperq
    Contributor

    @semenko this is my instinct as well. I suspect we should talk to someone at google about this.

  13. self-assigned this
    on Aug 11, 2016
  14. Hainish commented on Aug 11, 2016

    @Hainish
    Member

    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.

  15. cooperq commented on Aug 11, 2016

    @cooperq
    Contributor

    For me it has been around for a while, so I doubt it will go away on a point upgrade.

  16. 112 remaining items

  17. gloomy-ghost commented on Oct 29, 2016

    @gloomy-ghost
    Collaborator

    There is another report: #7456

  18. Pysis868 commented on Nov 10, 2016

    @Pysis868

    Just had the issue today (11/10/2016). Will check this new thread in #7456 in case it is a different root cause.

  19. Hainish commented on Nov 10, 2016

    @Hainish
    Member

    @Pysis868 what version of the extension are you using?

    On November 10, 2016 11:37:24 AM PST, Pysis868 notifications@github.com wrote:

    Just had the issue today (11/10/2016). Will check this new thread in
    #7456 in case it is a different root cause.

    You are receiving this because you modified the open/close state.
    Reply to this email directly or view it on GitHub:
    #5874 (comment)

    Sent from my Android device with K-9 Mail. Please excuse my brevity.

  20. Pysis868 commented on Nov 10, 2016

    @Pysis868

    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.

  21. mezmi commented on Dec 13, 2016

    @mezmi

    Still experiencing this issue on Chrome 55 (64bit) / Ubuntu 16. Privacy Badger fails to work properly either, both "corrupt" immediately after installation.

  22. Swimmer63 commented on Dec 13, 2016

    @Swimmer63

    Same here. This is a problem as of today.

  23. StoneLegion commented on Jan 17, 2017

    @StoneLegion

    Same issue here. Version 55.0.2883.87 m

  24. StoneLegion commented on Jan 17, 2017

    @StoneLegion

    @Hainish Please reopen.

  25. Hainish commented on Jan 17, 2017

    @Hainish
    Member

    @KaneHart this issue is tracking current "extension corrupted" reports: #7456

  26. dglezschez commented on Jan 24, 2017

    @dglezschez

    Updated Chrome today, still having the issue with HTTPSE
    Neither option given here (reinstall, restart, enable, Repair...) works. Windows 7 32bit

  27. iainbryden commented on Jan 26, 2017

    @iainbryden

    I also have "extension may be corrupted" errors. Two laptops, Windows 7, Chrome, version 2016.12.19

  28. Hainish commented on Jan 26, 2017

    @Hainish
    Member

    This issue is tracking current "extension corrupted" reports: #7456. Please issue reports there. Locking conversation.

  29. locked and limited conversation to collaborators on Jan 26, 2017
  30. ghost deleted a comment from on Jun 29, 2021
  31. ghost deleted a comment from on Jun 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions