I2P is an effort to build, deploy, and maintain a network to support secure and anonymous +
I2P is a project to build, deploy, and maintain a network supporting secure and anonymous communication. People using I2P are in control of the tradeoffs between anonymity, reliability, bandwidth usage, and latency. There is no central point in the network on which pressure can be exerted to compromise the integrity, security, or anonymity of the system. The network supports @@ -27,8 +24,8 @@ or even taken over to attempt more malicious attacks.
The network itself is message oriented - it is essentially a secure and anonymous IP layer, where messages are addressed to cryptographic keys (Destinations) and can be significantly larger than IP packets. Some example uses of the network include "eepsites" (webservers hosting normal web -applications within I2P), a BitTorrent port ("I2PSnark"), -or a distributed data store. With the help of mihi's I2PTunnel application, +applications within I2P), a BitTorrent client ("I2PSnark"), +or a distributed data store. With the help of the I2PTunnel application, we are able to stream traditional TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even streaming audio. Most people will not use I2P directly, or even need to know they're using it. Instead their view will be of one of the I2P enabled applications, or perhaps as a little controller @@ -60,7 +57,7 @@ messages. Client applications have their own cryptographic identifier ("Destina to send and receive messages. These clients can connect to any router and authorize the temporary allocation ("lease") of some tunnels that will be used for sending and receiving messages through the network. I2P has its own internal network database (using a modification of -the Kademlia algorithm) for scalable distributing routing and contact information securely.
+the Kademlia algorithm) for distributing routing and contact information securely.I2P initially began in Feb 2003 as a proposed modification to Freenet to allow it to use alternate transports, such as JMS, then grew into its own as an -'anonCommFramework' in April 2003, turning into I2P in July, with code being cut in earnest in August '03, -reaching the 0.2 release in September, 0.3 in March '04, and 0.4 in September '04. -Release 0.5 followed in early '05 and 0.6 in mid-'05. -I2P is currently moving forward according to +'anonCommFramework' in April 2003, turning into I2P in July, with code being written in earnest starting in August '03. +I2P is currently under development, folllowing the roadmap.
Anyone interested should @@ -146,4 +141,10 @@ There are currently no scheduled development meetings, however archives are available.
The current source is available in monotone.
+ ++See the Index to Technical Documentation +
+ {% endblock %} diff --git a/www.i2p2/pages/how_intro_de.html b/www.i2p2/pages/how_intro_de.html index 814583d0..9d1ba4c0 100644 --- a/www.i2p2/pages/how_intro_de.html +++ b/www.i2p2/pages/how_intro_de.html @@ -1,11 +1,6 @@ {% extends "_layout_de.html" %} {% block title %}Einführung in die Arbeitsweise von I2P{% endblock %} -{% block content %}Hinweis: Dieses "How" Dokument ist noch nicht vollständig aktualisiert -und enthält noch nicht die diversen Änderungen wie di neuen Tunnel -Routing und Verschlüsselungs Algorhytmen, die verschiedene -Probleme (inclusive benötigten Grundlagen, die -andereProbleme behoben) behoben haben, -und weitere Änderungen. +{% block content %}I2P ist ein Projekt, welches ein Netzwerk zum sicheren und anonymen Kommunizieren planen, aufbauen und betreuen wird. Nutzer von I2P haben die Kontrolle über die Verteilung zwischen Anonymität, diff --git a/www.i2p2/pages/how_threatmodel.html b/www.i2p2/pages/how_threatmodel.html index 91600512..cefbb3d2 100644 --- a/www.i2p2/pages/how_threatmodel.html +++ b/www.i2p2/pages/how_threatmodel.html @@ -132,14 +132,15 @@ defeat this attack exist, but may be prohibitively expensive (see: Tarzan's mimics or constant rate traffic). Most users are not concerned with this attack, as the cost of mounting it are extreme (and often require illegal activity). -However, the attack is still possible, and those who want to defend against it -would want to make appropriate countermeasures, such as not communicating with -unknown destinations, not publishing one's current leaseSet in the network -database, actively rerouting the associated tunnels 'mid stream', throttling the -inbound tunnels themselves, and/or using restricted routes with trusted links -to secure the local connection. +However, the attack is still possible, for example by an observer at +a large ISP or an Internet exchange point. +Those who want to defend against it +would want to take appropriate countermeasures, such as +setting low bandwidth limits, and using unpublished or encrypted leasesets for eepsites. +Other countermeasures, such as nontrivial delays and restricted routes, are +not currently implemented.
-As a partial defense against routers trying to route all the network's traffic, +As a partial defense against a single router or group of routers trying to route all the network's traffic, routers contain limits as to how many tunnels can be routed through a single peer. As the network grows, these limits are subject to further adjustment. Other mechanisms for peer rating, selection and avoidance diff --git a/www.i2p2/pages/jbigi.html b/www.i2p2/pages/jbigi.html index b8eb9ce9..31621094 100644 --- a/www.i2p2/pages/jbigi.html +++ b/www.i2p2/pages/jbigi.html @@ -1,10 +1,41 @@ {% extends "_layout.html" %} {% block title %}jbigi{% endblock %} -{% block content %}
Using JNI (Java Native Interface), a bit of C code (thanks ugha!), a little -manual work and a piece of chewing gum it is possible to make the public key -cryptography quite a bit faster.
+{% block content %} -Using JNI (Java Native Interface), a bit of C code (thanks ugha!), a little +manual work and a piece of chewing gum we have made several +cryptography operations quite a bit faster.
+ ++The speedup comes from the super-fast +GNU MP Bignum library (libgmp). +We use a single function from libgmp - +mpz_powm() +as a replacement for the +Java Math library's BigInteger modPow(). +As modPow() is a significant computational portion of many crypto operations, this is of significant benefit. +
+ ++The standard I2P installation includes about 20 versions of the library for different platforms, +each about 50KB, inside the jbigi.jar file. +The initialization of the JBigI library, including CPU identification, selection, and extraction +of the correct loadable module, is handled by the +NativeBigInteger class. +If no module is available for the current platform, the standard +Java Math library's BigInteger modPow() +is used. +
+ + +This works on Linux, and with a few changes in build.sh probably also on other platforms. FreeBSD has also been reported to work too. On Kaffee the speedup is very small, because it already uses native BitInteger internally. @@ -20,16 +51,16 @@ your processor. The latest GMP may also be used instead of GMP 4.2.2, but it hasn't been tested by us.
-crypto.elGamal.decrypt and
crypto.elGamal.encrypt are. The numbers are times in milliseconds. Copy these somewhere so you can compare
them later on.
@@ -82,10 +113,20 @@ report.libjbigi.so to your i2p directorycrypto.elGamal.decrypt and crypto.elGamal.encrypt
should be a lot faster.Feedback is appreciated
+crypto.elGamal.decrypt
und crypto.elGamal.encrypt abzulesen. Diese Zahlen sind Zeiten in Millisekunden.
Notiere dir diese Werte zum späteren Vergleich.
@@ -82,7 +82,7 @@ gebe uns das bitte bekannt.libjbigi.so in dein i2p Verzeichniscrypto.elGamal.decrypt und crypto.elGamal.encrypt
erheblich schneller sein.