The routers may also have different names. They do not appear to be running now.
http://www.noreply.org/tor-running-routers/
At 10:01 AM 4/15/2007, you wrote:
Oooooohhhh, clever. Obviously, the *first* thing that needs to happen is that the operator needs to start rebooting nodes so they end up with greatly differing uptimes. Concurently, assign someone on staff to start setting up nodes on widely separated networks. Start dropping machines in datacenters all across the continent. Then configure the nodes to either report different versions, or set up the servers on something other than FreeBSD machines. Then configure the nodes so that machines that are providing services have the appropriate exit policy. Finally, distribute the data-collection so that all traffic doesn't go through one node -- just have all the nodes pipe data into a collection node that's not part of the tor network at all. I'm impressed. 11% of the traffic with just 9 out of ~550 machines. Someone's demonstrated a proof-of-concept, and now can go back and request additional funding to really compromise such things. -- Watch, the feds will end up running most of the TOR network. Stewart Stremler
-- [EMAIL PROTECTED] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
