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

Closed (moved)
Open
Created Feb 12, 2006 by goodell@goodell

streams automatically attached to controller circuits

Currently, if a controller builds a circuit, then for all streams that Tor manages that match the exit policy for that circuit, Tor will gladly attach that stream to that circuit. This is sometimes desirable if a controller exists for the purpose of effecting an alternate selection algorithm for general-purpose circuits. However, this is undesirable if a controller exists for the purpose of constructing circuits for special use (e.g. Blossom). So, for each circuit we need a way of specifying whether Tor is allowed to automatically attach streams to that circuit. I propose that we have two classes of circuits: PUBLIC and PRIVATE, such that hen Tor is asked to automatically attach a stream to some circuit, it must choose from among PUBLIC circuits only. Circuits built via the controller with the EXTENDCIRCUIT command are considered PRIVATE by default. I propose an additional controller command, SETCIRCUITEXPOSURE, with the following syntax:

"SETCIRCUITEXPOSURE" SP CircuitID SP {0,1}

An argument of '0' sets the circuit with the specified CircuitID to PRIVATE. An argument of '1' sets the circuit with the specified CircuitID to PUBLIC.

[Automatically added by flyspray2trac: Operating System: All]

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