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

Closed (moved)
Open
Opened May 16, 2012 by cypherpunks@cypherpunks

Restore ExcludeEntryNodes feature

Seems that ExcludeEntryNodes configuration option was removed at some point (atleast 0.2.3.15-dev's "verify-config" rejects it).

It however would be nice to have it to avoid the "adversary can monitor entry and exit nodes" scenario which is very real in countries with few relays (which can be legally compelled to do such a thing) while still using the country's exitnodes (I don't have a problem with my traffic making a trip around the world and exiting to public Internet from the relay that my neighbour runs, I do however have a problem with my traffic entering the Tor network from the high-bandwidth relay with a Guard flag that my other neighbour, who happens to be an associate of the first neighbour, is running).

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#5903