Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Addon] HTTP Nowhere #188

Closed
nodiscc opened this issue Oct 5, 2016 · 8 comments
Closed

[Addon] HTTP Nowhere #188

nodiscc opened this issue Oct 5, 2016 · 8 comments

Comments

@nodiscc
Copy link
Contributor

nodiscc commented Oct 5, 2016

Would https://addons.mozilla.org/en-US/firefox/addon/http-nowhere/ be worth mentioning on the README? It blocks all connections not made over HTTPS. There is also an option to try forcing HTTPS when the site presents itself over a plaintext connection (similar to SMart HTTPS #187 (comment)), and a manual whitelist.

It does break a lot of websites which is expected since many hosts are not configured for SSL/TLS.
It does exactly what it says, block HTTP traffic.

Only major problem I found: it blocks connections to OCSP servers, which in turn also causes HTTPS connections to error. You have to manually whitelist them. In that regard #73 could be useful, I did not go this far.

https://github.com/cwilper/http-nowhere/ has some info.

@Atavic
Copy link

Atavic commented Oct 5, 2016

This whitelist seems a must for this addon to work properly. Without OCSP renewal, the browser will end finding expired CA Certs.

Another way is here.

@pyllyukko
Copy link
Owner

It does break a lot of websites

If this is the case, I think we shouldn't recommend it. I'm sure the world isn't ready for this yet :)

@Atavic
Copy link

Atavic commented Oct 16, 2016

I'd like to post a recent problem on Soundcloud: Vendor Downtime Causing Certificate Messages
caused by GlobalSign experiencing issues with OCSP and offering this solution because Invalid certificate remains in cache.

If a CDN Provider fails to flush its cache, the problem may still persist.

@ivan-kolmychek
Copy link

ivan-kolmychek commented Oct 16, 2016

HTTP Nowhere haven't been updated for a while already (Last Updated: September 16, 2013) and HTTPS Everywhere does have the support of blocking non-encrypted communications.

Maybe, that feature should be mentioned in readme instead of adding the notion of yet another addon? Especially given that HTTPS Everywhere is already recommended there. :)

screenshot_20161016_184613

@ivan-kolmychek
Copy link

On the second thought, I haven't found the manual whitelisting in HTTPS Everywhere, that's my bad.

@Atavic
Copy link

Atavic commented Oct 16, 2016

@ivan-kolmychek
Copy link

@Atavic I'm not sure they're working with "block all unencrypted requests", as I haven't tested it. Also, having a nice UI to edit the rules in-place, (like My Rules section in uMatrix config) would be nice.

So, that's why I'm not entirely sure you can replace HTTP Nowhere with HTTPS Everywhere at this point.

@nodiscc
Copy link
Contributor Author

nodiscc commented Oct 26, 2016

After some testing, HTTPS Everywhere's block all unencrypted requests seems to work as expected, I have sent a patch to update the documentation at #195.

This solves the problem for me and is preferable to HTTP Nowhere (1 less addon, same results + no apparent OCSP problems).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants