forked from I2P_Developers/i2p.www
Replaced the network comparsions image with a HTML table.
(ugha)
This commit is contained in:
@@ -29,13 +29,106 @@ of their use outside of academic environments.</p>
|
||||
<p>Stealing quite directly from the Tarzan paper, the following includes a quick
|
||||
comparison of Tarzan, Crowds, Onion Routing (OR), and I2P:</p>
|
||||
|
||||
<img src="http://dev.i2p.net/~jrandom/wiki/comparison.png" alt="Anonymous networks comparsion" />
|
||||
<table>
|
||||
<tr>
|
||||
<td style="width: 19%;"></td>
|
||||
<td style="width: 27%;" colspan="4">Bad first relay/router</td>
|
||||
<td style="width: 27%;" colspan="4">Bad intermediate relay/router</td>
|
||||
<td style="width: 27%;" colspan="4">Bad last relay/router</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Information exposed</td>
|
||||
<td><b>OR</b></td>
|
||||
<td><b>Crowds</b></td>
|
||||
<td><b>Tarzan</b></td>
|
||||
<td><b>I2P</b></td>
|
||||
|
||||
<td><b>OR</b></td>
|
||||
<td><b>Crowds</b></td>
|
||||
<td><b>Tarzan</b></td>
|
||||
<td><b>I2P</b></td>
|
||||
|
||||
<td><b>OR</b></td>
|
||||
<td><b>Crowds</b></td>
|
||||
<td><b>Tarzan</b></td>
|
||||
<td><b>I2P</b></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Sender activity</td>
|
||||
<td>Yes</td>
|
||||
<td>Maybe</td>
|
||||
<td>Maybe</td>
|
||||
<td><b>No</b></td>
|
||||
|
||||
<td>No</td>
|
||||
<td>No</td>
|
||||
<td>Maybe</td>
|
||||
<td><b>No</b></td>
|
||||
|
||||
<td>No</td>
|
||||
<td>No</td>
|
||||
<td>No</td>
|
||||
<td><b>No</b></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Recipient activity</td>
|
||||
<td>No</td>
|
||||
<td>Yes</td>
|
||||
<td>No</td>
|
||||
<td><b>No</b></td>
|
||||
|
||||
<td>No</td>
|
||||
<td>Yes</td>
|
||||
<td>No</td>
|
||||
<td><b>No</b></td>
|
||||
|
||||
<td>Yes</td>
|
||||
<td>Yes</td>
|
||||
<td>Yes</td>
|
||||
<td><b>No</b></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Sender content</td>
|
||||
<td>No</td>
|
||||
<td>Maybe</td>
|
||||
<td>No</td>
|
||||
<td><b>No</b></td>
|
||||
|
||||
<td>No</td>
|
||||
<td>No</td>
|
||||
<td>No</td>
|
||||
<td><b>No</b></td>
|
||||
|
||||
<td>No</td>
|
||||
<td>No</td>
|
||||
<td>No</td>
|
||||
<td><b>No</b></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Recipient content</td>
|
||||
<td>No</td>
|
||||
<td>Yes</td>
|
||||
<td>No</td>
|
||||
<td><b>No</b></td>
|
||||
|
||||
<td>No</td>
|
||||
<td>Yes</td>
|
||||
<td>No</td>
|
||||
<td><b>No</b></td>
|
||||
|
||||
<td>Yes</td>
|
||||
<td>Yes</td>
|
||||
<td>Yes</td>
|
||||
<td><b>No</b></td>
|
||||
</tr>
|
||||
</table>
|
||||
<p>(Original image at <a href="http://dev.i2p.net/~jrandom/wiki/comparison.png">
|
||||
http://dev.i2p.net/~jrandom/wiki/comparison.png</a>)</p>
|
||||
|
||||
<h2>TOR / Onion Routing</h2>
|
||||
<i><a href="http://freehaven.net/tor/">[TOR]</a>
|
||||
<a href="http://www.onion-router.net">[Onion Routing]</a></i>
|
||||
<p>
|
||||
TOR and Onion Routing are both anonymizing proxy networks, allowing people
|
||||
<p>TOR and Onion Routing are both anonymizing proxy networks, allowing people
|
||||
to tunnel out through their low latency mix network. The two primary
|
||||
differences between TOR / OnionRouting and I2P are again related to differences
|
||||
in the threat model and the out-proxy design (though TOR is working to provide
|
||||
@@ -72,8 +165,7 @@ database</a> and <a href="how_peerselection">peer selection</a>.</p>
|
||||
<i><a href="http://mixminion.net/">[Mixminion]</a>
|
||||
<a href="http://mixmaster.sourceforge.net/">[Mixmaster]</a></i>
|
||||
|
||||
<p>
|
||||
Mixminion and Mixmaster are networks to support anonymous email against a very
|
||||
<p>Mixminion and Mixmaster are networks to support anonymous email against a very
|
||||
powerful adversary. I2P aims to provide an adequate means to meet their threat
|
||||
model as we reach I2P 3.0 along side the needs of low latency users, providing
|
||||
a significantly larger anonymity set. As with TOR and Onion Routing above,
|
||||
@@ -81,8 +173,8 @@ both Mixminion and Mixmaster take the directory based approach as well.</p>
|
||||
|
||||
<h2>Freenet</h2>
|
||||
<i><a href="http://freenetproject.org/">[Freenet]</a></i>
|
||||
<p>
|
||||
Freenet is a fully distributed, peer to peer anonymous publishing network.
|
||||
|
||||
<p>Freenet is a fully distributed, peer to peer anonymous publishing network.
|
||||
As such, generic anonymous communication over it requires the use of the global
|
||||
blackboard model - storing data somewhere that the recipient will then check
|
||||
for a message. Freenet also does not support the concept of user defined delays -
|
||||
@@ -95,8 +187,7 @@ low latency communication.</p>
|
||||
<h2>JAP</h2>
|
||||
<i><a href="http://anon.inf.tu-dresden.de/index_en.html">[JAP]</a></i>
|
||||
|
||||
<p>
|
||||
JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing web requests,
|
||||
<p>JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing web requests,
|
||||
and as such it has a few centralized nodes (participants in the cascade) that blend
|
||||
and mix requests from clients through the sequence of nodes (the cascade) before
|
||||
proxying out onto the web. The scope, threat model, and security is substantially
|
||||
@@ -110,5 +201,4 @@ on the network. Even though the method of this attack was later found to be ill
|
||||
in the German courts, the fact that the data was successfully collected is the
|
||||
concern. Courts change their minds based upon circumstance, and this is evidence that
|
||||
if a government body or intelligence agency wanted to, they could gather the data, even
|
||||
if it may be found inadmissible in some courts later)
|
||||
</p>
|
||||
if it may be found inadmissible in some courts later)</p>
|
||||
|
Reference in New Issue
Block a user