Files
tor/changes
Arthur Edelstein 2bd91dbd34 Don't consider a port "handled" by an isolated circuit.
Previously, circuit_stream_is_being_handled incorrectly reported
that (1) an exit port was "handled" by a circuit regardless of
whether the circuit was already isolated in some way, and
(2) that a stream could be "handled" by a circuit even if their
isolation settings were incompatible.

As a result of (1), in Tor Browser, circuit_get_unhandled_ports was
reporting that all ports were handled even though all non-internal
circuits had already been isolated by a SOCKS username+password.

Therefore, circuit_predict_and_launch_new was declining to launch
new exit circuits. Then, when the user visited a new site in Tor
Browser, a stream with new SOCKS credentials would be initiated,
and the stream would have to wait while a new circuit with those
credentials could be built. That wait was making the
time-to-first-byte longer than it needed to be.

Now, clean, not-yet-isolated circuit(s) will be automatically
launched ahead of time and be ready for use whenever a new stream
with new SOCKS credentials (or other isolation criteria) is
initiated.

Fixes bug 18859. Thanks to Nick Mathewson for improvements.
2017-12-06 14:18:41 -08:00
..
2017-11-27 09:09:16 -05:00
2017-09-12 10:28:45 -04:00
2017-08-28 14:43:42 -04:00
2017-06-26 11:26:59 -04:00
2017-08-08 10:09:54 -04:00
2017-06-16 14:26:50 -04:00
2017-06-16 14:03:02 -04:00
2017-07-17 21:44:59 +00:00
2017-06-27 18:25:48 -04:00
2017-06-27 10:31:03 -04:00
2017-07-13 18:16:22 +00:00
2017-08-08 09:13:45 -04:00
2017-08-21 15:04:35 -04:00
2017-09-20 09:45:03 -04:00
2017-07-31 20:40:23 -04:00
2017-11-30 11:52:40 -05:00