Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #264

Closed (moved)
(moved)
Open
Created Mar 04, 2006 by goodell@goodell

controller denied access to streams in SENTCONNECT state

If a stream is in the SENTCONNECT state but has not succeeded yet, then the controller has no means of reattaching this stream to another circuit. For example,

attachstream 266 62 555 Connection is not managed by controller.

Clearly, the controller ought to be able to tell Tor to terminate the SENTCONNECT state early. We can do this in two ways:

  1. Presume that the only reason to terminate SENTCONNECT early is to attach a stream to a different circuit. This means that we are really interested in extending the capability of the ATTACHSTREAM directive to support reattaching even streams in the SENTCONNECT state.

  2. Create a DETACHSTREAM controller command that can explicitly detach a stream from a circuit (perhaps this should only work if the stream is in the SENTCONNECT state), causing the stream to enter the DETACHED state, thus becoming suitable for reconnection via the controller.

[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
Time tracking