Just a heads up that there <b>has</b> been torrc validation in arm for quite some time now. Warnings about this issue (unused entries due to duplicates) have been given since release 1.2.2 (11/8/09, so bit less than a year now). I just tested and it has been giving warnings about ExcludeNodes all this time (root cause is that only entries with LINELIST and LINELIST_S in src/or/config.c can be duplicates).<br>
<br>If others have ideas for additional validation I can do on user's torrc files then I'd love to know. Cheers! -Damian<br><br><div class="gmail_quote">On Fri, Sep 10, 2010 at 1:05 AM, Sebastian Hahn <span dir="ltr"><<a href="mailto:mail@sebastianhahn.net">mail@sebastianhahn.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im"><br>
On Sep 10, 2010, at 9:57 AM, Scott Bennett wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
On Fri, 10 Sep 2010 03:39:44 -0400 Roger Dingledine <<a href="mailto:arma@mit.edu" target="_blank">arma@mit.edu</a>><br>
wrote:<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
As I understand it, we changed no behavior except printing out a warn<br>
for people who had multiple lines, to tell them that they're expecting<br>
behavior that they're not getting.<br>
</blockquote>
<br>
[extremely shocked pause...]<br>
.<br>
.<br>
.<br>
Roger, please tell me that you're joking. I have *never* had the<br>
understanding from reading the documentation in all of the years I've been<br>
using tor that only a single line of each type would be used. How, then,<br>
are we to exclude all of the nodes that we find unacceptable for use in our<br>
own circuits?<br>
If what you say is actually the case, then it would seem that a problem<br>
described on this list on many occasions during the last few years may, in<br>
fact, have been due to this horrible limitation. Several of us have complained<br>
on numerous occasions that adding a node to one list or the other and sending<br>
SIGHUP to tor (or restarting it) failed to prevent that node from being used<br>
in the manner that we had expressly excluded. If what you say is indeed the<br>
case, then it is a truly awful design bug.<br>
</div></blockquote>
<br>
Yup, that's the actual behaviour. Good thing we added the warn, otherwise<br>
it might have gone unnoticed longer.<br><font color="#888888">
<br>
Sebastian</font><div><div></div><div class="h5"><br>
***********************************************************************<br>
To unsubscribe, send an e-mail to <a href="mailto:majordomo@torproject.org" target="_blank">majordomo@torproject.org</a> with<br>
unsubscribe or-talk in the body. <a href="http://archives.seul.org/or/talk/" target="_blank">http://archives.seul.org/or/talk/</a><br>
</div></div></blockquote></div><br>