Chrome on Windows disables non-web store HTTPS Everywhere on restart #819

Closed
jsha opened this Issue Dec 13, 2014 · 16 comments

Comments

Member

jsha commented Dec 13, 2014

Steps to reproduce:

  1. In Chrome on Windows, install HTTPS Everywhere directly from EFF (download the .crx, drag and drop into Extensions page).
  2. Restart Chrome.

Expected result:

HTTPS Everywhere stays installed.

Actual result:

On next startup, a notice appears in the upper right saying "Unsupported extensions disabled. To make Chrome safer, we disabled some extensions that aren't listed in the Chrome Web Store and may have been added without your knowledge.

  • HTTPS Everywhere"

On the Extensions page, HTTPS Everywhere is greyed out, disabled, and the checkbox to re-enable it is greyed out. Enabling developer mode doesn't fix it, nor does dragging in the .crx again. Deleting the extension and dragging back in the .crx works until the next restart.

We should ask Google about this.

This comment has been minimized.

Show comment Hide comment
@semenko

semenko Dec 13, 2014

Contributor

Chrome no longer allows any outside of webstore extensions, due to lots of malware abuse.

You can sorta keep them enabled by turning on Developer Mode (you need to actually use the features of developer mode -- otherwise chrome will warn you & disable developer mode). You can also install them via a Win. GPO.

Contributor

semenko commented Dec 13, 2014

Chrome no longer allows any outside of webstore extensions, due to lots of malware abuse.

You can sorta keep them enabled by turning on Developer Mode (you need to actually use the features of developer mode -- otherwise chrome will warn you & disable developer mode). You can also install them via a Win. GPO.

This comment has been minimized.

Show comment Hide comment
@semenko

semenko Dec 13, 2014

Contributor

This comment has been minimized.

Show comment Hide comment
@alguar

alguar Dec 13, 2014

Thank you for the tip I appreciate the info.

Date: Sat, 13 Dec 2014 09:11:06 -0800
From: notifications@github.com
To: https-everywhere@noreply.github.com
Subject: Re: [https-everywhere] Chrome on Windows disables non-web store HTTPS Everywhere on restart (#819)

See: http://blog.chromium.org/2013/11/protecting-windows-users-from-malicious.html

There are some alternatives, though none seem applicable here: https://developer.chrome.com/extensions/external_extensions


Reply to this email directly or view it on GitHub.

                  =

alguar commented Dec 13, 2014

Thank you for the tip I appreciate the info.

Date: Sat, 13 Dec 2014 09:11:06 -0800
From: notifications@github.com
To: https-everywhere@noreply.github.com
Subject: Re: [https-everywhere] Chrome on Windows disables non-web store HTTPS Everywhere on restart (#819)

See: http://blog.chromium.org/2013/11/protecting-windows-users-from-malicious.html

There are some alternatives, though none seem applicable here: https://developer.chrome.com/extensions/external_extensions


Reply to this email directly or view it on GitHub.

                  =

This comment has been minimized.

Show comment Hide comment
@NewEraCracker

NewEraCracker Jan 1, 2015

There are two options to workaround this.

One is extracting the CRX to a new folder in the computer and use programing mode to load the extension from the folder.

Another one is, the one I use for archival purposes, download the CRX from Chrome webstore using "Give me CRX": https://chrome.google.com/webstore/detail/give-me-crx/acpimoebmfjpfnbhjgdgiacjfebmmmci

Apparently there is some method of certificate authentication in CRX files and those downloaded from eff's website mismatch the copies at google's servers.

Regards,
NewEraCracker

There are two options to workaround this.

One is extracting the CRX to a new folder in the computer and use programing mode to load the extension from the folder.

Another one is, the one I use for archival purposes, download the CRX from Chrome webstore using "Give me CRX": https://chrome.google.com/webstore/detail/give-me-crx/acpimoebmfjpfnbhjgdgiacjfebmmmci

Apparently there is some method of certificate authentication in CRX files and those downloaded from eff's website mismatch the copies at google's servers.

Regards,
NewEraCracker

This comment has been minimized.

Show comment Hide comment
@semenko

semenko Mar 26, 2015

Contributor

Closing this since ~unfixable -- Google has worked hard to block non-webstore installed extensions due to malware.

Contributor

semenko commented Mar 26, 2015

Closing this since ~unfixable -- Google has worked hard to block non-webstore installed extensions due to malware.

@semenko semenko closed this Mar 26, 2015

This comment has been minimized.

Show comment Hide comment
@McKinleyGroup

McKinleyGroup Apr 12, 2016

Hi jsha,
Hi Semenko,
https://chrome.google.com/webstore/detail/https-everywhere/gcbommkclmclpchllfjekcdonpmejbdp

Version: 2016.4.4
Updated: April 4, 2016

Should do just fine! 👍

I hope this helps. :-)

Hi jsha,
Hi Semenko,
https://chrome.google.com/webstore/detail/https-everywhere/gcbommkclmclpchllfjekcdonpmejbdp

Version: 2016.4.4
Updated: April 4, 2016

Should do just fine! 👍

I hope this helps. :-)

This comment has been minimized.

Show comment Hide comment
@buaabyl

buaabyl Jul 21, 2016

But can't access Google domain in China:(

buaabyl commented Jul 21, 2016

But can't access Google domain in China:(

@ghost

This comment has been minimized.

Show comment Hide comment
@ghost

ghost Sep 3, 2016

i found HTTPS Everywhere 2016.9.1 corrupted in google chrome version
capture-20160904-022436

ghost commented Sep 3, 2016

i found HTTPS Everywhere 2016.9.1 corrupted in google chrome version
capture-20160904-022436

This comment has been minimized.

Show comment Hide comment
@nikw92

nikw92 Sep 5, 2016

@chamzank - I found a workaround for this latest issue. With the extension installed, go to the Chrome Webstore page for HTTPS Everywhere. There will be prompt saying that "This extension has been disabled in Chrome" with a button to enable it. Enable it from there and it should work.

nikw92 commented Sep 5, 2016

@chamzank - I found a workaround for this latest issue. With the extension installed, go to the Chrome Webstore page for HTTPS Everywhere. There will be prompt saying that "This extension has been disabled in Chrome" with a button to enable it. Enable it from there and it should work.

@ghost

This comment has been minimized.

Show comment Hide comment
@ghost

ghost Sep 5, 2016

not work..

ghost commented Sep 5, 2016

not work..

This comment has been minimized.

Show comment Hide comment
@dld-r00f

dld-r00f Sep 13, 2016

Try to delete extention and install it again with Chrome Webstore. Then enable it as described above. [chrome version 53.0.2785.113 m (64-bit)]

Try to delete extention and install it again with Chrome Webstore. Then enable it as described above. [chrome version 53.0.2785.113 m (64-bit)]

This comment has been minimized.

Show comment Hide comment
@q158073378252010

q158073378252010 Sep 23, 2016

@chamzank 我也有同样的问题!不排除扩展bug

@chamzank 我也有同样的问题!不排除扩展bug

This comment has been minimized.

Show comment Hide comment
@Raciel14

Raciel14 Sep 24, 2016

gracias McKinleyGroup este enlace funciona para la extension en chrome dejo el link: https://chrome.google.com/webstore/detail/https-everywhere/gcbommkclmclpchllfjekcdonpmejbdp
que Dios los bendiga... 👍

gracias McKinleyGroup este enlace funciona para la extension en chrome dejo el link: https://chrome.google.com/webstore/detail/https-everywhere/gcbommkclmclpchllfjekcdonpmejbdp
que Dios los bendiga... 👍

This comment has been minimized.

Show comment Hide comment
@nullQ

nullQ Sep 30, 2016

gracias McKinleyGroup este enlace funciona para la extension en chrome dejo el link: https://chrome.google.com/webstore/detail/https-everywhere/gcbommkclmclpchllfjekcdonpmejbdp
que Dios los bendiga... 👍

thx , it's useful

nullQ commented Sep 30, 2016

gracias McKinleyGroup este enlace funciona para la extension en chrome dejo el link: https://chrome.google.com/webstore/detail/https-everywhere/gcbommkclmclpchllfjekcdonpmejbdp
que Dios los bendiga... 👍

thx , it's useful

This comment has been minimized.

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