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

Closed
Open
Opened Sep 17, 2011 by Trac@tracbot

Default Relay Exit Policy

There are two opposite points of view as to what should be the default setting for running a Relay: Either no exits should be allowed (a no-exit Relay) or all the exits should be allowed.

Less than half of all Relays are exit Relays considerably diminishing Tor's capabilities. So setting the default Relay configuration to no-exit would be counter-productive to Tor's purpose. On the other hand, permitting all exits does expose Relay operators to increased risk. It appears then a compromise of setting the default Relay configuration to exits for unsecure and secure websites would let Relay operators provide a valuable and essential service while at the same time reducing the risk to themselves.

Trac:
Username: ancientmariner

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