[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[freehaven-cvs] add mixmaster network table, move to separate file
Update of /home/freehaven/cvsroot/doc/routing-zones
In directory moria.mit.edu:/home2/arma/work/freehaven/doc/routing-zones
Modified Files:
routing-zones.tex
Added Files:
network-tables.tex
Log Message:
add mixmaster network table, move to separate file
--- NEW FILE: network-tables.tex ---
\begin{table} \caption{Tor nodes as of January 2004}
\label{table:tor-network}
\renewcommand{\arraystretch}{1.3}
\begin{center}
\begin{tabular}[b]{| l | l | l | l | c |}
\hline
Name & IP address & Country & Zone & Exit node? \\
\hline
anon.inf.tu-dresden.de & 141.76.46.90 & Germany & & \\
anon.itys.net & 209.221.142.117 & US & & Y \\
c3po.cs.byu.edu & 128.187.170.212 & US & & Y \\
cassandra.eecs.harvard.edu & 140.247.60.133 & US & & Y \\
code13.unixpunx.org & 205.158.23.142 & US & & \\
gw.provos.org & 66.92.17.34 & US & & Y \\
incognito.shmoo.com & 69.5.78.151 & US & & Y \\
moria.mit.edu & 18.244.0.188 & US & & Y \\
nymip.org & 66.92.0.206 & US & & Y \\
ovmj.org & 128.10.19.51 & US & & Y \\
peertech.org & 207.36.86.132 & US & & Y \\
petra.felter.org & 69.20.9.201 & US & & Y \\
tor.noreply.org & 62.116.124.106 & Austria & & \\
www.peerfear.org & 66.93.132.237 & US & & Y \\
\hline
\end{tabular}
\end{center}
\end{table}
\begin{table} \caption{Mixmaster nodes as of January 2004}
\label{table:mixmaster-network}
\renewcommand{\arraystretch}{1.3}
\begin{center}
\begin{tabular}[b]{| l | l | l | l | c |}
\hline
Name & IP address & Country & Zone & Exit node? \\
\hline
aarg & 69.9.134.82
amigo & 212.67.202.215
anon & 24.147.172.248
antani & 195.110.124.18
ashcroft & 66.79.46.86
austria & 212.124.142.99
banana & 82.133.6.115
bigapple & 167.206.5.3
bikikii & 216.80.122.14
bunker & 213.129.65.104
cf & 208.210.149.14
chicago & 65.31.179.120
citrus & 168.150.177.152
cmeclax & 208.150.110.21
congo & 216.154.65.55
cracker & 207.15.209.4
cripto & 195.250.236.58
cthulu & 67.121.201.38
dingo & 208.180.124.28
discord & 141.12.220.23
dizum & 194.109.206.210
dot & 81.0.225.26
edo & 213.254.4.10
freedom & 205.241.45.100
frell & 62.109.75.33
futurew & 212.66.104.81
gbnq & 213.133.98.183
george & 212.171.49.198
harmless & 66.92.53.74
hastio & 80.34.205.8
hermes & 208.42.19.154
italy & 62.211.72.26
itys & 209.221.142.117
krotus & 69.17.45.166
lcs & 18.26.0.254
lemuria & 213.191.86.35
liberty & 216.218.240.134
mercler & 213.133.111.165
metacolo & 193.111.87.9
nikto & 62.155.144.81
nitemare & 128.176.188.172
panta & 217.155.84.182
paranoia & 213.140.29.37
randseed & 216.218.240.190
riot & 213.254.16.33
rot26 & 62.245.184.24
senshi & 213.165.64.100
starwars & 62.211.216.127
tonga & 213.130.163.34
vger & 66.166.203.164
willers & 128.107.241.167
\hline
\end{tabular}
\end{center}
\end{table}
Index: routing-zones.tex
===================================================================
RCS file: /home/freehaven/cvsroot/doc/routing-zones/routing-zones.tex,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- routing-zones.tex 26 Jan 2004 06:24:35 -0000 1.7
+++ routing-zones.tex 26 Jan 2004 06:55:41 -0000 1.8
@@ -302,49 +302,23 @@
Here we should also describe the current list of nodes for each of the
mix networks we analyze. A table would be appropriate.
-\begin{table} \caption{Tor nodes as of January 2004}
-\label{table:expected-delivery}
-\renewcommand{\arraystretch}{1.3}
-\begin{center}
-\begin{tabular}[b]{| l | l | l | l | c |}
-\hline
-Name & IP address & Country & Zone & Exit node? \\
-\hline
-anon.inf.tu-dresden.de & 141.76.46.90 & Germany & & \\
-anon.itys.net & 209.221.142.117 & US & & Y \\
-c3po.cs.byu.edu & 128.187.170.212 & US & & Y \\
-cassandra.eecs.harvard.edu & 140.247.60.133 & US & & Y \\
-code13.unixpunx.org & 205.158.23.142 & US & & \\
-gw.provos.org & 66.92.17.34 & US & & Y \\
-incognito.shmoo.com & 69.5.78.151 & US & & Y \\
-moria.mit.edu & 18.244.0.188 & US & & Y \\
-nymip.org & 66.92.0.206 & US & & Y \\
-ovmj.org & 128.10.19.51 & US & & Y \\
-peertech.org & 207.36.86.132 & US & & Y \\
-petra.felter.org & 69.20.9.201 & US & & Y \\
-tor.noreply.org & 62.116.124.106 & Austria & & \\
-www.peerfear.org & 66.93.132.237 & US & & Y \\
-\hline
-\end{tabular}
-\end{center}
-\end{table}
\subsection{AS-level path estimation}
-If the initiator of a mix-net path had access to an up-to-date routing
-table of every network containing mix nodes, then it could construct a
+If Alice had access to an up-to-date routing
+table from every network containing mix nodes, she could construct a
reasonable estimate of the AS-level path fairly easily: to discover the
-AS-level path between nodes $i$ and $i+1$, for example, the initiator
+AS-level path between nodes $i$ and $i+1$, for example, she
could look at $i$'s routing table and determine the AS path associated
with the route that is the longest prefix match for $i+1$'s IP address.
-Unfortunately, the initiator cannot generally ask for routing tables for
+Unfortunately, Alice cannot generally ask for routing tables for
each of the mix nodes when it wishes to construct a mix tunnel. First,
-the initiator's act of requesting a routing table from a particular
-network might raise the suspicion of an eavesdropper (particularly if an
-initiator asks for a large number of routing tables, since each full
+her act of requesting a routing table from a particular
+network might raise the suspicion of an eavesdropper (particularly if she
+asks for a large number of routing tables, since each full
routing table is approximate 10 megabytes). Second, asking each network
that contains a mix node for its current routing table is likely to be
quite slow, given the size of routing tables; additionally, as routes
***********************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe freehaven-cvs in the body. http://freehaven.net/