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

Closed (moved)
Open
Opened Apr 10, 2014 by Trac@tracbot

Exit not using one hop circuit to Directory Server

I've set up a lab to learn about Tor. All nodes running within Xen 6.2 on FreeBSD 10 running Tor version 2.4.19.

All clients can build circuits and functionality looks as expected. However, while entry and relay nodes use the encrypted, one-hop circuit to communicate with the Directory Server, the exit node does not. The exit node communicates directly with the dir port on the directory server (http). I'm using tcpdump -nvvv -A on the specific interfaces to see the traffic.

All nodes in the lab are essentially clones. The torrc file is changed on each node to reflect client, entry, relay, and exit roles. The only difference between the nodes that use the one-hop circuilt and the one that doesn't is the "accept" policy on the exit node. I don't see how that relates, but when I remove the "accept" policy and add a policy to "reject :" the one-hop circuit is then used . I've gone over this quite a bit. It may be a bug.

Trac:
Username: bburley

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