Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #8534
Closed (moved) (moved)
Open
Issue created Mar 20, 2013 by Peter Eckersley@pde

[CHROME] Cookies can bleed to/from incognito mode

This would be an urgent bug, except for the fact that HTTPS Everywhere does not run in Chrome's incognito mode unless the user manually enables it in about:extensions.

Bram reported seeing google login state bleeding across the incognito/normal boundary.

We need to repro this, check whether it's specific to Google (Chrome has its own notion of "logged in", so that might be relevant), and fix.

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