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

Closed (moved)
Open
Opened Nov 15, 2016 by Trac@tracbot

Disposable Exit Nodes

Just like bridges are designed to get past blocking of guard nodes, it would be great to see a similar concept but this time for exit relays. I'm suggesting making available the possibility to setup "throwaway exit relays" that,

  1. last for a specific period of time (say 1 day),

  2. from where one can configure to access specific sites (for example, one uses the Tor Button to use Exit X to access www.example.com),

  3. aren't -- obviously -- published in the official directories, but it can be seen whether such IP was an exit at a time t using the standard tool for that purpose, but this information is not disclosed until after the ending period of the disposable exit relay,

  4. can be made either public (available to the Tor Project to distribute them, just like it does with bridges) or private.

I think that even if the public type may be extremely difficult, especially seeing how it is difficult to even have the rate of new bridges being greater than the rate at which the adversary learns them, it would still be a good idea to have the private type.

Trac:
Username: madystar

To upload designs, you'll need to enable LFS and have an 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#20676