EFF's HTTPS Everywhere removed from Chrome app store | Hacker News Reader

EFF's HTTPS Everywhere removed from Chrome app store

chrome.google.com

85 pointszurn33 comments

CWS entry: https://chrome.google.com/webstore/detail/https-everywhere/g...

It says "item removed by author"

I saw that it updated yesterday (thanks to this awesome extension https://chrome.google.com/webstore/detail/extensions-update-...)

Could you tell us what that extension does, iPad users visiting the link just get an OS not supported error.

Forces the browser to use https version (i.e. the encrypted version) of site you're trying to access instead of http wherever possible.

I don't think this is some conspiracy or anything, they just released a new version[0] and it's possible it broke something. Also, it's still available at the EFF website[1], and if you look in the FAQ, it's not available in the Mozilla store either[2], so this may have been intentional on the part of EFF.

[0] https://www.eff.org/files/Changelog.txt

[1] https://www.eff.org/https-everywhere

[2] https://www.eff.org/https-everywhere/faq#amo

When I try installing it off the eff website, I get this message in Chrome: "Apps, extensions, and user scripts cannot be added from this website." No option to override or ignore the message :-/

go to Tools->Extensions first

You have to download the extension file and drag it into your extensions list.

Absolutely annoying this ability to override messages. The same issue is with expired/not authorized server certificates on Chrome. I need to copy session ids around just to trick Chrome into accessing some stupid research database. I hate nanny browsers.

You need to download the extension, open the extensions settings, then drag the .crx file into there.

You can also use this command line flag:

--enable-easy-off-store-extension-install

It caused internet problems for me. It wouldn't load any website while it was enabled on Chrome, today.

I visited bbc.co.uk about 20 minutes ago, and started getting requests which apparently came from the BBC asking me to allow an Apple ID SSL certificate. I wonder if this is why.

It was asking me which SSL client cert I wanted to present to identify to beta.bbc.co.uk. In my case I have my StartCom one and a OSG science one.

Yep I got this too, beta.bbc.co.uk 443 cert etc.

No other site would load either until I disabled the extension.

It's been working fine for me for months. No problems today, either.

I actually just had to disable it an hour ago, It wouldn't let me go to any website.

And then I found this article...

Same. It prevented pages loading and caused Chrome to completely lock up.

Same here, had to disable

same here. disabled long ago.

Ya, the plugin causes lots of problems. It can mangle headers on XHR to sites that aren't using https. Spent a day debugging problems that turned out to just be https everywhere.

Oh my that was it! I had been wondering about it and disabled plenty of extensions, but not this one. Also made me realize that I should use Firefox more often again...

Yup. The extension was creating a huge CPU load on my Mac. Started happening yesterday and tested each Chrome extension to find this was the one creating the issue.

Wouldn't be surprised. I just had my app removed. All it did was show you your true ip when you're using a proxy, to show how your address leaks. They banned it. Do not see how that violates any TOS..

What is the name of the app?

Chrome Web Store: Removal notification for Proxy IP Test ==> http://proxytest.info

They broke it and removed it temporarily, nothing to see here.

Why didn't they simply revert to the previous version instead of removing it?

App store may not have that ability.

Probably, but shouldn't they be able to list a reason why?

Hey, I'm the maintainer of HTTPS Everywhere.

Last night we released a Chromium update that had a critical bug that broke the browser. As soon as we discovered this we removed it from the Chrome store temporarily until we could release an update.

We just released an update that fixes this bug, and it's back in the store again: https://chrome.google.com/webstore/detail/https-everywhere/g...

I can't confirm this is related, but I'd had browser / XOrg issues on Linux, including error messages related to HTTPS Everywhere:

https://plus.google.com/104092656004159577193/posts/6ZBjctvo...

Even after a window manager restart (which addressed other issues), re-enabling HTTPS Everywhere killed page-loading.

That "mixed content will be disabled" could very well have killed a lot of pages, though it's not clear to me if this would account for other issues I was seeing (apparently some sort of memory overflow in "bo map" on my graphics card/driver).

Chrome tries to use hardware acceleration features of your video card and in my experience it rarely works on Linux. If you visit about:gpu and see anything mentioning it making use of hardware acceleration, try going to settings, and search for 'hardware', and uncheck the 'use hardware acceleration when available' setting.

(Disclaimer: I know many of the people who are responsible for the related code and they get sad when I recommend things like this, but in my opinion a reliable browser is more important than WebGL occasionally working.)

Reply on news.ycombinator.com