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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed
Open
Opened Mar 05, 2018 by Damian Johnson@atagar

Treat 'ExitRelay 0' as a reject-all policy

Oops! Most folks use 'ExitPolicy reject :' to flag their relay as being a non-exit, but turns out that tor has another option that does the same thing...

https://www.torproject.org/docs/tor-manual.html.en#ExitRelay

We should change the Controller's get_exit_policy() method to provide a reject-all policy when this is set. Caught thanks to Gary on tor-relays...

https://lists.torproject.org/pipermail/tor-relays/2018-March/014741.html

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