You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Implement all of HTTPS Finder functionality inside HTTPS-Everywhere #2718
It is a lot more likely to discover possible targets for a new rule or a changed rule, if you get an automated note while browsing the non-encrypted version of the site.
While i don't think a automated ruleset should be made without additional manual work, a notification "there is content you could encrypt" would be really helpfull.
States could be:
green: using TLS
red: can't be requested over TLS
orange: could be secured, but isn't
purple: could be used with TLS but uses a self signed or expired or otherwise not trusted certificate
I'd be very interested to see this implemented. HTTPS-E could have an option that let's you choose between:
"Finder off", just like now
"Finder on (manually)", if on HTTP but HTTPS would be possible it shows a green dot telling us "hey, here is TLS possible", if user clicks on green dot then it will reload the page with HTTPS
"Finder on (auto)", like above, but it redirects automatically, but the user can click on the icon to force back to HTTP (for example if HTTPS has different content or breaks functionality)
And while the Finder is on (manually or auto), it only is active if there is no rule present, of course (no need to waste resources on the Finder for already knowingly working websites).
I think this should be natural first step for browsers [with deprecating http}(https://blog.mozilla.org/security/2015/04/30/deprecating-non-secure-http/). Sadly no browser has done anything as far as I am aware and it would be nice if HTTPS Everywhere could do that.
@genodeftest: I'm aware of these problems and I did not suggest to switch on such a finder-functionality by default. To me the suggestions above by @numismatika and @foobar13373 make sense as long as they are optional and inactive by default. Also, when somebody wants to activate the finder, there could be a warning showing the text from the FAQ.
However, I do understand that this is not a high priority issue.
Combining this with "Block all HTTP requests" (which HTTPS-E already can) like suggested in #3230 is actually a pretty good idea. This could be added as a first step and in a later release release allow more fine-grained controlling.
Activity
numismatika commentedon Aug 29, 2015
It is a lot more likely to discover possible targets for a new rule or a changed rule, if you get an automated note while browsing the non-encrypted version of the site.
While i don't think a automated ruleset should be made without additional manual work, a notification "there is content you could encrypt" would be really helpfull.
I think something like https://addons.mozilla.org/de/firefox/addon/sixornot/ would be great, multi-colored status of the encryption for a certain object request in a tree-view.
States could be:
green: using TLS
red: can't be requested over TLS
orange: could be secured, but isn't
purple: could be used with TLS but uses a self signed or expired or otherwise not trusted certificate
ldgbc commentedon Sep 2, 2015
There seem to be little interest in adding these feature. It better to just hope for a HTTPS Finder fork as the original developer quit.
foobar13373 commentedon Sep 3, 2015
I'd be very interested to see this implemented. HTTPS-E could have an option that let's you choose between:
And while the Finder is on (manually or auto), it only is active if there is no rule present, of course (no need to waste resources on the Finder for already knowingly working websites).
I'd love to see this!
numismatika commentedon Sep 12, 2015
i wouldn't call it lack of interest, most of the people working on this are busy with getting letsencrypt into shape.
stryx commentedon Sep 23, 2015
Just wanted to say that I would also highly appreciate such functionality inside HTTPS-Everywhere.
genodeftest commentedon Sep 23, 2015
This might be a bad idea. See the FAQ for details: Why use a whitelist of sites that support HTTPS? Why can't you try to use HTTPS for every last site, and only fall back to HTTP if it isn't available?
Mikaela commentedon Sep 23, 2015
I think this should be natural first step for browsers [with deprecating http}(https://blog.mozilla.org/security/2015/04/30/deprecating-non-secure-http/). Sadly no browser has done anything as far as I am aware and it would be nice if HTTPS Everywhere could do that.
stryx commentedon Sep 23, 2015
@genodeftest: I'm aware of these problems and I did not suggest to switch on such a finder-functionality by default. To me the suggestions above by @numismatika and @foobar13373 make sense as long as they are optional and inactive by default. Also, when somebody wants to activate the finder, there could be a warning showing the text from the FAQ.
However, I do understand that this is not a high priority issue.
foobar13373 commentedon Nov 21, 2015
Combining this with "Block all HTTP requests" (which HTTPS-E already can) like suggested in #3230 is actually a pretty good idea. This could be added as a first step and in a later release release allow more fine-grained controlling.
rugk commentedon Dec 5, 2015
Possibly related to #2115
rezad1393 commentedon May 5, 2016
https-finder in longer working with firefox last version.
I used self-signed one that worked before but now stopped working.
pipboy96 commentedon Mar 28, 2019
Outdated, duplicate of #13041.