This repository has been archived by the owner on Jan 4, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 114
First-party storage isolation in Tor mode #468
Labels
Comments
diracdeltas
added a commit
that referenced
this issue
Jan 31, 2018
darkdh
added a commit
that referenced
this issue
Feb 1, 2018
… options fix #468 fix #464 Auditors: @bridiver, @riastradh-brave, @diracdeltas
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Desired goal: For parity with Tor Browser (https://www.torproject.org/projects/torbrowser/design/#identifier-linkability), we should implement strict first-party isolation for all persistent data: cookies, cache, HSTS state, permissions, DOM cookies, etc.
One way to do this is to use
ContentBrowserClient::GetStoragePartitionConfigForSite
to create isolated in-memory storage partitions for each Site Instance. Assuming we go with Option 5 in #464, each Site Instance should have at most one origin associated with it.The text was updated successfully, but these errors were encountered: