In Chrome on Windows, install HTTPS Everywhere directly from EFF (download the .crx, drag and drop into Extensions page).
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.
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.
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.
@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.
Steps to reproduce:
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.
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.