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

Closed (moved)
Open
Opened May 23, 2016 by teor@teor

Make sure clients almost always use ntor

Update: All clients should use ntor for almost everything The only exceptions are during the hidden service protocol. Client to intro and hidden service to rendezvous should still be able to use TAP.


isis asks in #1744 (moved):

 // XXXprop#188 Why do we not care if it's ntor if it's only one hop?

I think it's because one-hop circuits were originally used only for directory fetches, which are authenticated by signature (and not private).

But with RSOS, maybe we should require all one-hop paths to have ntor. I need to talk to a cryptographer about this.

See the populate_cpath function for details.

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