Files
tor/changes
Nick Mathewson 4851de554d Do not automatically ignore Fast/Stable for exits when ExitNodes is set
This once maybe made sense when ExitNodes meant "Here are 3 exits;
use them all", but now it more typically means "Here are 3
countries; exit from there."  Using non-Fast/Stable exits created a
potential partitioning opportunity and an annoying stability
problem.

(Don't worry about the case where all of our ExitNodes are non-Fast
or non-Stable: we handle that later in the function by retrying with
need_capacity and need_uptime set to 0.)
2011-04-26 23:54:16 -04:00
..
2011-02-10 17:11:06 -05:00
2011-01-25 17:37:37 -05:00
2011-01-25 18:45:13 -05:00
2011-01-25 17:49:02 -05:00
2010-11-30 19:19:36 -05:00
2011-03-01 10:05:18 +01:00
2011-01-15 19:42:17 +01:00
2011-01-10 12:12:11 -05:00
2011-01-25 18:26:49 -05:00
2011-01-25 15:54:51 -05:00
2011-02-11 17:02:26 +01:00
2011-02-08 09:10:14 -05:00
2011-03-09 16:22:18 -05:00
2011-03-18 17:13:43 +01:00
2011-03-27 05:38:53 +02:00
2011-04-26 15:36:17 +02:00
2011-04-15 05:35:30 +02:00
2011-04-18 13:53:13 -07:00
2011-04-04 03:52:58 -04:00
2011-03-08 18:15:17 -05:00
2011-03-25 16:28:37 -04:00
2011-03-15 09:48:26 -07:00
2010-12-15 22:35:07 -05:00