Am I correct to assume that your message below means that when
UseEntryGuards is set to 1 it causes Tor to ignore the value of StrictEntryNodes?<br clear="all"><br>The manual doesn't state that UseEntryGuards takes precedence over StrictEntryNodes. Which is unfortunate because UseEntryGuards defaults to 1, which means that StrictEntryNodes is, by default, ignored.<br>
--<br>Fran<br><br><div class="gmail_quote">On Mon, Dec 22, 2008 at 4:27 AM, zmj <span dir="ltr"><<a href="mailto:zangmj@gmail.com">zangmj@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Tor has 3 default EntryGuards. They are different from EntryNodes which are defined by users.<br>Tor picks EntryGuards by itself.<br><dl compact><dt><b>UseEntryGuards </b><b>0</b>|<b>1</b>
</dt><dd>If this option is set to 1, we pick a few long-term entry servers, and try
to stick with them. This is desirable because constantly changing servers
increases the odds that an adversary who owns some servers will observe a
fraction of your paths. (Defaults to 1.) </dd></dl>
<p>
</p><dl compact><dt><b>NumEntryGuards </b><i>NUM</i>
</dt><dd>If UseEntryGuards is set to 1, we will try to pick a total of NUM routers as
long-term entries for our circuits. (Defaults to 3.) </dd><dt><br></dt></dl>look here: <a href="https://www.torproject.org/tor-manual-dev.html.en" target="_blank">https://www.torproject.org/tor-manual-dev.html.en</a><div>
<div></div><div class="Wj3C7c"><br><br><div class="gmail_quote">
On Wed, Dec 17, 2008 at 2:02 AM, Fran Litterio <span dir="ltr"><<a href="mailto:flitterio@gmail.com" target="_blank">flitterio@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div>On Tue, Dec 16, 2008 at 12:32 PM, I wrote:<br></div></div><div class="gmail_quote"><div><div></div><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm running Vidalia 0.1.10 and Tor 0.2.0.32 (r17346) on Windows XP.<br>
<br>
I stopped Tor from the Vidalia GUI, and manually edited Vidalia's<br>
"torrc" file, adding these two lines at the bottom:<br>
<br>
StrictEntryNodes 1<br>
EntryNodes BostonUCompSci,FSF,moria1,SelfEvident,superbad,fuga,augrime,askatasuna,VSvTZGO7UPj4yh8,conf555nick,desync,phobos<br>
<br>
After re-starting Tor from the Vidalia GUI, I see circuits that have<br>
entry nodes that are _not_ from the above list. In fact, nearly all<br>
circuits have entry nodes that are not from the above list.</blockquote></div></div><div><br>Update: If I add the following four lines to the bottom of Vidalia's "torrc" file, then Tor honors the StrictExitNodes + ExitNodes options, but it ignores the StrictEntryNodes + EntryNodes options:<div>
<br>
<br> StrictEntryNodes 1<br> EntryNodes BostonUCompSci,FSF,moria1,SelfEvident<br></div> StrictExitNodes 1<br> ExitNodes BostonUCompSci,FSF,moria1,SelfEvident<br><br>Although, Tor seems to only use the first of the specified ExitNodes. Shouldn't it round-robin between them?<br>
--<br>Fran<br><br></div></div>
</blockquote></div><br>
</div></div></blockquote></div><br>