Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Browser Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 834
    • Issues 834
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor BrowserTor Browser
  • Issues
  • #3246
Closed
Open
Issue created May 20, 2011 by Mike Perry@mikeperryDeveloper

Isolate HTTP cookies according to first and third party domain contexts

Right now, we've set Tor Browser to block third party cookies. This will probably break some sites. There is a less intrusive option described at https://wiki.mozilla.org/Thirdparty that we should use.

Rebase and test existing patches (originating from https://bugzilla.mozilla.org/show_bug.cgi?id=565965)

Revise requirements according to preliminary tests and devise a broad test plan.

Reimplement and retest to guarantee proper isolation without severely impeding cookie dependent applications.

Document the implementation and optionally a contrast of browser cookie handling.

Pave the way towards a improved privacy panel including a new cookie inspector and API supporting such UI.

Note: This is a metaticket composed of work items in child tickets.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking