[tor-bugs] #5830 [Analysis]: Write tool to automate web queries to Tor; and use Stem to track stream/circ allocation and results (was: Write stream/circ event parser to track circuit use)

Tor Bug Tracker & Wiki blackhole at torproject.org
Wed Jan 16 19:27:06 UTC 2013


#5830: Write tool to automate web queries to Tor; and use Stem to track
stream/circ allocation and results
----------------------+-----------------------------------------------------
 Reporter:  arma      |          Owner:       
     Type:  task      |         Status:  new  
 Priority:  normal    |      Milestone:       
Component:  Analysis  |        Version:       
 Keywords:  bounty    |         Parent:  #5752
   Points:            |   Actualpoints:       
----------------------+-----------------------------------------------------
Description changed by arma:

Old description:

> As part of #5752 we need to know how many circuits we're making now, how
> many we're discarding early because a stream didn't work, etc.
>
> I think we could do this as a Tor controller that watches stream and
> circuit events.
>
> I expect we'll also discover that we don't export enough info via the
> control protocol to make good conclusions; in that case we'll want to
> modify Tor to export this info.
>
> [I'm not sure what component to put this ticket in, so I picked Torflow
> since it's already pretty good at parsing tor controller output.]

New description:

 As part of #5752 we need to know how many circuits we're making now, how
 many we're discarding early because a stream didn't work, etc.

 This is a two-part project: first is a tool to automatically make a series
 of requests to Tor, in a repeatable way, and second is a Tor controller
 script, probably using Stem, that watches stream and circuit events (and
 maybe more), and tracks which streams get allocated to which circuits, how
 many total circuits are made, how quickly results return, and other
 statistics. Then we would change the underlying Tor, replay the same set
 of requests, and know what circuit behaviors to expect.

 I expect we'll also discover that we don't export enough info via the
 control protocol to make good conclusions; in that case we'll also want to
 modify Tor to export this info.

--

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


More information about the tor-bugs mailing list