gratuitous change blocks upgrade to 0.2.2.15-alpha :-(

[Sebastian Hahn]

On Sep 10, 2010, at 9:57 AM, Scott Bennett wrote:

>     On Fri, 10 Sep 2010 03:39:44 -0400 Roger Dingledine <arma at mit.edu>
> wrote:
>> As I understand it, we changed no behavior except printing out a warn
>> for people who had multiple lines, to tell them that they're  
>> expecting
>> behavior that they're not getting.
>
>     [extremely shocked pause...]
> 	.
> 	.
> 	.
>     Roger, please tell me that you're joking.  I have *never* had the
> understanding from reading the documentation in all of the years  
> I've been
> using tor that only a single line of each type would be used.  How,  
> then,
> are we to exclude all of the nodes that we find unacceptable for use  
> in our
> own circuits?
>     If what you say is actually the case, then it would seem that a  
> problem
> described on this list on many occasions during the last few years  
> may, in
> fact, have been due to this horrible limitation.  Several of us have  
> complained
> on numerous occasions that adding a node to one list or the other  
> and sending
> SIGHUP to tor (or restarting it) failed to prevent that node from  
> being used
> in the manner that we had expressly excluded.  If what you say is  
> indeed the
> case, then it is a truly awful design bug.

Yup, that's the actual behaviour. Good thing we added the warn,  
otherwise
it might have gone unnoticed longer.

Sebastian
***********************************************************************
To unsubscribe, send an e-mail to majordomo at torproject.org with
unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/