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

Closed (moved)
Open
Opened Jan 17, 2017 by Roger Dingledine@arma

Should we stop setting AuthDirBadExitCC?

Sebastian points out that the original reasoning for #4923 (moved), which is that Vidalia users in Iran and Syria were clicking "make me a relay" without really understanding the implications, are long past.

I looked over #4923 (moved) for hints about our previous mental state, and I found two points worth reading and thinking about:

"if we learned that a given relay was logging all traffic that its users generate, and putting those logs up on its website, would we badexit that relay?" and "badexit is a blunt instrument and this makes us look like tools of the US government's bullshit and ill thought out internet policy talking points."

In summary, I am now thinking that I've run out of good reasons to argue for keeping the AuthDirBadExitCC sy,ir line in my torrc file.

What do other badexit-voting dir auth operators think?

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