diff options
author | Nick Mathewson <nickm@torproject.org> | 2013-02-14 12:06:59 -0500 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2013-02-14 12:06:59 -0500 |
commit | 1070a720ad7f45fa82b77be0512056a06e535b72 (patch) | |
tree | 2ff76f12390f5f7c88b1b62080ebe73b5e58873c /src/or/circuitbuild.c | |
parent | 91027218e29090b18d42e1868367cc2a9e149900 (diff) | |
download | tor-1070a720ad7f45fa82b77be0512056a06e535b72.tar.gz tor-1070a720ad7f45fa82b77be0512056a06e535b72.zip |
Be more robust when excluding existing nodes as new dirguards
In addition to rejecting them post-hoc, avoid picking them in the
first place. This makes us less likely to decide that we can't add
guards at all.
Diffstat (limited to 'src/or/circuitbuild.c')
-rw-r--r-- | src/or/circuitbuild.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/or/circuitbuild.c b/src/or/circuitbuild.c index 163afd3d29..c2f395338d 100644 --- a/src/or/circuitbuild.c +++ b/src/or/circuitbuild.c @@ -3397,6 +3397,7 @@ choose_good_entry_server(uint8_t purpose, cpath_build_state_t *state) }); } /* and exclude current entry guards and their families, if applicable */ + /*XXXX025 use the using_as_guard flag to accomplish this.*/ if (options->UseEntryGuards) { SMARTLIST_FOREACH(get_entry_guards(), const entry_guard_t *, entry, { |