[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
* Roger Dingledine (arma@xxxxxxx) wrote:
> On Fri, Jul 28, 2006 at 01:34:56AM -0400, Marcel wrote:
> > I have set ExcludeNodes flyingboy, etc. Then I tried
> > ExcludeNodes $75D31DF7F1579F78FF8635107ECE23F1B7CCFE80, etc.
> > for my client.
> > How can it be i still have flyingboy selected each and every day as entry
> > node? It this a bug, has flyingboy on purpose defeated this feature?
> > Just wondering.
> Yes, it's a bug. If you choose a node as one of your entry guards,
> and later you add it to ExcludeNodes, then it won't be thrown out.
Thanks for the explanation.
> It's on the todo list.
> (We didn't pay it much mind, because we don't use ExcludeNodes, and
> we're thinking of de-emphasizing it even more. Letting users play with
> their routes on a wide scale is probably bad for their anonymity, and
> definitely bad for load balancing across servers.)
Interesting. Maybe I should consider stopping using ExcludeNodes and use
instead a huge list of ExitNodes along with StrictExitNodes.
Ex: If server isn't in China, add it to ExitNodes.