#9543: weird behaviour when MaxCircuitDirtiness is set to a high value
--------------------+-------------------------------------------------------
Reporter: ra | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor | Version: Tor: 0.2.3.25
Keywords: | Parent:
Points: | Actualpoints:
--------------------+-------------------------------------------------------
I tested this with the rttprober script[0] which opens circuits and
attaches multiple streams to them. Each stream connects to 127.0.0.1,
fails and quits. When I set MaxCircuitDirtiness to the default value (600)
and tell the script to open circuits and run 1000 stream-probes on each
circuit, it completes for most of the circuits. When I set
MaxCircuitDirtiness to a very large value (tested with 2147483647 and
1073741823) almost all circuits where closed with reason FINISHED before
all probes where run. Using a MaxCircuitDirtiness of 10000 works as
expected though.
[0] https://bitbucket.org/ra_/tor-rtt/src
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9543>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs