[tor-bugs] #3457 [Tor Client]: Expose more circuit state-change events to controllers

Tor Bug Tracker & Wiki torproject-admin at torproject.org
Fri Dec 23 14:09:04 UTC 2011

#3457: Expose more circuit state-change events to controllers
 Reporter:  rransom      |          Owner:  rransom           
     Type:  enhancement  |         Status:  needs_review      
 Priority:  normal       |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Client   |        Version:                    
 Keywords:               |         Parent:                    
   Points:               |   Actualpoints:                    

Comment(by rransom):

 Replying to [comment:6 nickm]:
 > Why do we need a new event type for this?  It seems like something we
 could do just fine with the current CIRC events.  We can't add new
 CircStatus entries (I think), but we can just send back the previous
 CircStatus with the new purpose.

 I want to indicate to the controller what caused the event to be sent.
 CIRC2 events are also a bit ‘louder’ than CIRC events, and will become
 even louderer if we add an INTRODUCE CIRC2 event type to tell controllers
 of a hidden service when an INTRODUCE2 cell has been received.

 We can't add new CircStatus values for CIRC events because (a) the spec
 doesn't specifically allow it, and (b) Vidalia won't handle them sensibly
 (and I don't know how any controller could).  Adding a new event type
 seemed much better.

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3457#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

More information about the tor-bugs mailing list