Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
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

Closed

Description

@crisalis

HTTPS Finder is bound to die for several reasons and I think even some HTTPS-Everywhere developers use it.

Activity

  1. numismatika commented on Aug 29, 2015

    @numismatika
    Contributor

    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

  2. ldgbc commented on Sep 2, 2015

    @ldgbc
    Contributor

    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.

  3. foobar13373 commented on Sep 3, 2015

    @foobar13373

    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'd love to see this!

  4. numismatika commented on Sep 12, 2015

    @numismatika
    Contributor

    i wouldn't call it lack of interest, most of the people working on this are busy with getting letsencrypt into shape.

  5. stryx commented on Sep 23, 2015

    @stryx

    Just wanted to say that I would also highly appreciate such functionality inside HTTPS-Everywhere.

  6. Mikaela commented on Sep 23, 2015

    @Mikaela
    Contributor

    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.

  7. stryx commented on Sep 23, 2015

    @stryx

    @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.

  8. foobar13373 commented on Nov 21, 2015

    @foobar13373

    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.

  9. rugk commented on Dec 5, 2015

    @rugk
    Contributor

    Possibly related to #2115

  10. rezad1393 commented on May 5, 2016

    @rezad1393

    https-finder in longer working with firefox last version.
    I used self-signed one that worked before but now stopped working.

  11. pipboy96 commented on Mar 28, 2019

    @pipboy96
    Contributor

    Outdated, duplicate of #13041.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions