nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-24 12:23:32 +01:00
Code Issues Packages Projects Releases Wiki Activity

Correct comment explaining why tor2web mode should disable entry guards

Browse Source
This commit is contained in:
Robert Ransom 2012-09-18 16:38:01 -04:00
parent 9d3e497edb
commit d1c4cf2f5a
1 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
src/or/config.c
View File

@ -2523,15 +2523,13 @@ options_validate(or_options_t *old_options, or_options_t *options,
} }
if (options->Tor2webMode && options->UseEntryGuards) { if (options->Tor2webMode && options->UseEntryGuards) {
/* Tor2WebMode is incompatible with EntryGuards in two ways: /* tor2web mode clients do not (and should not) use entry guards
* * in any meaningful way. Further, tor2web mode causes the hidden
* - Tor2WebMode uses its guard nodes as rend and intro points. * service client code to do things which break the path bias
* This makes tor2web users fingerprintable by their continued * detector, and it's far easier to turn off entry guards (and
* selection of the same 3 nodes for these circuits (their guard * thus the path bias detector with it) than to figure out how to
* nodes). * make a piece of code which cannot possibly help tor2web mode
* * users compatible with tor2web mode.
* - Tor2WebMode makes unexpected use of circuit path lengths
* in ways that prevent us from applying the PathBias defense.
*/ */
log_notice(LD_CONFIG, log_notice(LD_CONFIG,
"Tor2WebMode is enabled; disabling UseEntryGuards."); "Tor2WebMode is enabled; disabling UseEntryGuards.");