Https-everywhere: Update hsts-prune to use preload policies

Created on 20 Nov 2017  路  5Comments  路  Source: EFForg/https-everywhere

Type: feature request

The HSTS preload list has added a tag to indicate under which policy a given domain was added (see https://github.com/chromium/hstspreload.org/issues/111 and this diff from the Chromium codebase).

It would be great if hsts-prune.js could use this new info to remove more domains. More specifically, domains with a special policy, such as google, custom or public-suffix-requested should be removed automatically, without the need to check for the presence of the required headers.

Related: https://github.com/EFForg/https-everywhere/issues/13235

ruleset-testing

Most helpful comment

I don't like the "special policies" used by some browser vendors for their own domains. There is no guarantee that they're all handled well across all browsers. It's also not clear what policies are added or kept in forks of these browsers.

All 5 comments

cc @Hainish

@Bisaloo In discussions with the Chrome team, I weighed in favor of this change, and I think it's a step forward. I'd like the extra assurance that Firefox will also follow this policy, as well.

I don't like the "special policies" used by some browser vendors for their own domains. There is no guarantee that they're all handled well across all browsers. It's also not clear what policies are added or kept in forks of these browsers.

@J0WI Same here, especially since Chrome devs have deprecated static pinning of CA keys for every website except Google-owned ones.

Was this page helpful?
0 / 5 - 0 ratings