[tor-bugs] #3443 [Tor Client]: Client with low CBT can't switch to a bridge if it's slow
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Mon Apr 30 22:34:24 UTC 2012
#3443: Client with low CBT can't switch to a bridge if it's slow
------------------------+---------------------------------------------------
Reporter: arma | Owner:
Type: defect | Status: new
Priority: major | Milestone: Tor: 0.2.3.x-final
Component: Tor Client | Version:
Keywords: regression | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by mikeperry):
I think you did the branch wrong. https://github.com/grubWare/Tor-0.2.3.14
-alpha-custom-networkResetLowered/commits/master has only one commit, and
it seems like compilation garbage.
I don't buy your natural ping time argument. That is what CBT is doing
already if you look at the math, and it's also an orthogonal discussion to
the current bug. The doubling issue is probably also a different bug.
Again, I see two solutions to the current ticket:
1. We could just hack the timeout code not to start counting time until a
TLS connection exists.
2. we add in an "abandon the timeout data if all guards change" check to
circuit_build_times_network_check_changed()
Do we want one or both? Or some unknown option 3?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3443#comment:19>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list