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 835
    • Issues 835
    • 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
  • #23955
Closed
Open
Issue created Oct 23, 2017 by cypherpunks@cypherpunks

Set "ConnectionPadding 1" by default to unify padding behavior for Tor Browser users

Netflow padding was implemented by Mike Perry and merged for Tor 0.3.1.x, however by default it is only enabled with relays that have version bigger or equal to 0.3.1.x.

https://www.torproject.org/docs/tor-manual.html.en#ConnectionPadding

As a result, since Tor version distribution for guard nodes is significantly different it means that some Tor Browser users will have different network fingerprint.

Of course even if they have it's not really that harmful but enabling it by default may not prove harmful either.

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