[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Blocking particular Entry/Exit nodes
- To: or-talk@xxxxxxxx
- Subject: Blocking particular Entry/Exit nodes
- From: yousifnet <yousifnet@xxxxxxxxx>
- Date: Wed, 13 Sep 2006 12:46:27 +0300
- Delivered-to: archiver@seul.org
- Delivered-to: or-talk-outgoing@seul.org
- Delivered-to: or-talk@seul.org
- Delivery-date: Wed, 13 Sep 2006 05:46:45 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=GzPCh04X5Mg2FX1JysPJNM3D2tMdVIfA6Sqm7Ur1xoQJmSGUSLJ6JOgGh+uvIx5raNN3y9xJfS82dUN9VRQdW3l67m0r7YxvOCxxbFKDMsXzDIORLViFp7k5btDJMXXIF+kQyQmhQLhD8aeFlJ9+NYiqCZrRgkACvrH9AGX67Uw=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
Hi all,
I guess some of you know of the ability to track down a certain
request through Tor if someone controls both the entry and the exit
node and look for the timing of the request. Although the probability
of that happening is not large, it still shouldn't be ignored.
I am wondering, is it possible to block certain nodes from being an
entry/exit node, or perhaps impliment an IP block. For example, I
don't want to use entry nodes with an IP 10.*.*.* or with the name
BadNode.
If it's not possible then perhaps the developers of Tor should allow
the user to add lines to torrc.conf to automatically block nodes in
future versions. e.g.
BlockNodes BadNode, BadNode2
I feel helpless when it comes to picking which Entry/Exit nodes to
use/to not use. Maybe the developers should give back some control to
the user :). Or was it deliberately done this way?
ps. no spell checker