Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

should we further mitigate threats of identifiers in local storage because some mechanisms won't clear all local storage? #43

Open
npdoty opened this issue May 22, 2020 · 0 comments

Comments

@npdoty
Copy link
Collaborator

npdoty commented May 22, 2020

See https://github.com/w3ctag/security-questionnaire/issues/80 on potentially recommending further limitations on local state and identifiers.

The Mitigating Fingerprinting guidance does first note that we shouldn't add unnecessary additional local storage, and then notes the mitigation of simultaneous clearing of local state.
https://w3c.github.io/fingerprinting-guidance/#clearing-all-local-state

And the severity section notes that persistence is one factor (in particular, that things not easily cleared are of special importance), but still notes it as fingerprinting surface even when clearable. is there something additional we should say here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant