[tor-bugs] #23374 [Core Tor/Tor]: Circuit dirtiness is inconsistant with MaxCircuitDirtiness

Tor Bug Tracker & Wiki blackhole at torproject.org
Thu Sep 21 20:53:10 UTC 2017


#23374: Circuit dirtiness is inconsistant with MaxCircuitDirtiness
--------------------------+------------------------------------
 Reporter:  Jaym          |          Owner:  (none)
     Type:  defect        |         Status:  needs_information
 Priority:  Low           |      Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |        Version:
 Severity:  Minor         |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------
Changes (by nickm):

 * status:  new => needs_information


Comment:

 Three observations:

 1) Hm. In shadow, maybe we should define TIME_IS_FAST?

 The approx_time() value is updated from second_elapsed_callback(), so if
 it's getting 9 seconds behind time(NULL), that's a very strange sign.

 2) When you say,

 > It happens only for 2 begin cells containing same IP

 That's probably good -- it means IsolateDestAddr is working.
 (IsolateDestAddr is the one that means "never sent connections to
 different targets over the same circuit.")

 3) Have you patched Tor to allow "MaxCircuitDirtiness 1" ?  By default, it
 should be saying:

 {{{
 Sep 21 16:52:54.348 [warn] MaxCircuitDirtiness option is too short;
 raising to 10 seconds.
 }}}

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


More information about the tor-bugs mailing list