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
  • #27879

Closed (moved)
Open
Opened Sep 27, 2018 by traumschule@traumschule

Remove pathbias code

This is blocked by #26886 (moved).

mikeperry in comment:7:issue:27228:

I think it is fine to remove all of the pathbias code once we get a tagging resistant cipher in place, such as https://gitweb.torproject.org/torspec.git/tree/proposals/295-relay-crypto-with-atl.txt Hoping for further guidance in any case i will just try this. We'll see if i end up with a stable tor.

Once this is merged unresolved pathbias bugs become obsolete and it might make #16764 (moved), #21084 (moved), #25783 (moved) easier.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#27879