Opened 9 years ago

Closed 7 years ago

#3282 closed enhancement (wontfix)

Extend the new Python Torperf to talk to tor's control port

Reported by: karsten Owned by: tomb
Priority: Medium Milestone:
Component: Archived/Torperf Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: #2565 Points:
Reviewer: Sponsor:


After finishing #3281, we should extend Torperf to talk to the control ports of the tor processes it started before. Torperf should use TorCtl for this task similar to and In fact, we can probably re-use most of the code from these two files.

Connecting to tor's control port has two purposes that have to be performed by the new Torperf: First, Torperf may have to influence tor's guard node selection algorithm depending on its configuration, and second, Torperf will have to process control port events and write them to a local .extradata file.

Assigning to tomb upon request.

Child Tickets

Change History (1)

comment:1 Changed 7 years ago by karsten

Resolution: wontfix
Status: newclosed

There's a new attempt to rewrite Torperf, starting with a design document. Closing all tickets related to the earlier attempt, because they're not relevant anymore.

Note: See TracTickets for help on using tickets.