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.

Clarify relationship with HSTS in FAQ #8187

Closed

Description

@pinobatch

The section "Why does HTTPS Everywhere include rules for sites like PayPal that already require HTTPS on all their pages?" in the FAQ currently states the following with regard to sites that redirect from HTTP to HTTPS:

(Note that HTTPS Everywhere currently does not include a comprehensive list of such sites, which are mainly financial institutions.)

In a comment to another pull request, jeremyn wrote with respect to lines 70 and 92 of a proposed change to the FAQ:

I'm not entirely sure what "Such a list would largely be redundant to the HSTS preload list." means.

The FAQ currently implies that HTTPS Everywhere's rewriting primarily covers sites that do not yet redirect all cleartext HTTP requests to HTTPS. It also includes a few sites that do redirect, primarily banks, because those are especially sensitive to first-visit SSL stripping. Both HTTPS Everywhere and the HSTS preload list are measures against first-visit SSL stripping. But if a site is in the HSTS preload list of all browsers that support HTTPS Everywhere, it doesn't need to be in HTTPS Everywhere. This is why in the section "How do I add my own site to HTTPS Everywhere?", the FAQ recommends instead getting onto the HSTS preload list in order to protect even those users who do not use HTTPS Everywhere.

So to clarify HTTPS Everywhere's role as a supplement to HSTS, I propose the following:

  • In "How do I get support for an additional site in HTTPS Everywhere?", add a notice for webmasters to read the section "How do I add my own site to HTTPS Everywhere?" below.
  • In "Why does HTTPS Everywhere include rules for sites like PayPal that already require HTTPS on all their pages?", mention why "HTTPS Everywhere currently does not include a comprehensive list of such sites".

Activity

  1. jeremyn commented on Jan 12, 2017

    @jeremyn
    Contributor

    I'm actually not sure what "(Note that HTTPS Everywhere currently does not include a comprehensive list of such sites, which are mainly financial institutions.)" is trying to say in the current FAQ. I think it means that HTTPS doesn't distinguish or make a sub-list of covered domains that already force a redirect from plain HTTP to HTTPS. I would remove that line from the FAQ answer because it's confusing, but maybe it was added after EFF got a lot of questions on that specific point. I don't know.

    I don't want to clutter the FAQ by linking one FAQ to another FAQ fifty lines down. Maybe instead we could merge How do I get support for an additional site in HTTPS Everywhere? and How do I add my own site to HTTPS Everywhere?

    Also @pinobatch you may find these two issues relevant: #7126 for HSTS and #7707 for documentation. I think @Hainish has a personal to-do to try to sort all the documentation out.

  2. Hainish commented on Jan 13, 2017

    @Hainish
    Member

    FYI: My main concern is to sort out the documentation with CONTRIBUTING.md, the progress for which you can track with this (currently work in progress) PR #8193

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions