Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

Disable 3p dynamic HSTS | Expect-CT | PKP headers #925

Closed
jumde opened this issue Feb 27, 2019 · 3 comments
Closed

Disable 3p dynamic HSTS | Expect-CT | PKP headers #925

jumde opened this issue Feb 27, 2019 · 3 comments

Comments

@jumde
Copy link
Contributor

jumde commented Feb 27, 2019

Description:

Headers like "Strict-Transport-Security", "Expect-CT", "Public-Key-Pins", "Public-Key-Pins-Report-Only" can be used for fingerprinting in 3p context.

For more info: brave/brave-browser#3419

Repro steps:

  1. Disable HTTPS Everywhere
  2. Navigate to https://jsfiddle.net/x5mqb807/ - This loads content from avatars2.githubusercontent.com which sets the Strict-Transport-Security header.
@jumde jumde added the privacy label Feb 27, 2019
@tildelowengrimm
Copy link

Is the solution that we'll remember headers set by third parties but only apply them to first parties, or that we'd only remember or apply when the site is a first party?

@jumde
Copy link
Contributor Author

jumde commented Feb 27, 2019

@ShivanKaul
Copy link
Collaborator

Public Key Pins and Expect-CT are deprecated headers, and for HSTS, we follow Safari which does partition the HSTS cache.

@ShivanKaul ShivanKaul closed this as not planned Won't fix, can't repro, duplicate, stale May 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants