Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #23955

Closed (moved)
Open
Opened 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 admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#23955