I agree this is something that should be done with the tor controller. Another thought for people is that they may be going through servers that are known to be used by intelligence organizations or have a high logging rate. One problem you might encounter when going through tor servers on educational/corporate networks is the high amount of logging that happens. Theoretically, it shouldn't matter but realistically it does. I suggest windows users check out peerguardian (peerguardian.sourceforge.net) to block these servers if you wish. (Linux people check out MoBlock). I did notice that NATO C3 ran a tor server which is enough to convince me to watch who I connect to. Ringo Kamens
On 2/26/07, Robert Hogan <[EMAIL PROTECTED]> wrote:
On the face of it, forcing tor to be 'geo-diverse' (dread word) is fairly straightforward. The option is called NodeFamily. Ask the author of your favourite tor controller to implement something like 'Enforce Geoographical Diversity' and instruct tor to treat all servers in the same country as a nodefamily. Of course, you could also do it yourself using: https://torstat.xenobite.eu/index.php?SortBy=G The chances are Tor itself will never do this for you - it has kludge written all over it. Also while it might mitigate looping through the same ISP at entry and exit, it will probably make you statistically *more* likely to hit a global adversary, such as, erm, world gentil(l?)ery. Thoughts anyone? Worth doing? -- KlamAV - An Anti-Virus Manager for KDE - http://www.klamav.net TorK - A Tor Controller For KDE - http://tork.sf.net
