Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #20915

Closed (moved)
(moved)
Open
Created Dec 07, 2016 by Georg Koppen@gk

Web developer network tab breaks first-party isolation in some cases

There are rare cases where the first-part isolation breaks if the Web developer Network tab is open. This got first reported on our blog: https://blog.torproject.org/blog/tor-browser-65a5-released#comment-224102

Steps to reproduce (works both in the stable and the alpha series on Linux at least):

  1. Start a fresh Tor Browser and set the Torbutton log level to "3"
  2. Open the Network tab in the Web developer console (Ctrl + Shift + Q)
  3. Go to https://torproject.org
  4. Reload the page with the arrow in the URL bar

Result:

Torbutton INFO: tor SOCKS isolation catchall: https://www.torproject.org/images/onion-heart.png via --unknown--:de6a28fb71abeba4febbbdde61de345e

It is actually only the request for the onion heart that is affected. And having the Network tab open is crucial for reproducing the bug.

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