I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

updates for 0.8.3

Browse Source
This commit is contained in:
zzz
2011-01-20 15:09:52 +00:00
parent 3773c8a9a2
commit e2e744cd16
4 changed files with 23 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
www.i2p2/pages/faq.html
View File

@ -464,6 +464,10 @@ router advanced configuration option <tt>i2cp.tcp.bindAllInterfaces=true</tt> an
<i>May be disabled or changed on the i2ptunnel page in the router console.
May also be configured to be bound to a specific interface or all interfaces.
</i></li>
<li><b>4445:</b> HTTPS proxy
<i>May be disabled or changed on the i2ptunnel page in the router console.
May also be configured to be bound to a specific interface or all interfaces.
</i></li>
<li><b>6668:</b> IRC proxy
<i>May be disabled or changed on the i2ptunnel page in the router console.
May also be configured to be bound to a specific interface or all interfaces.
@ -479,12 +483,11 @@ router advanced configuration option <tt>i2cp.tcp.bindAllInterfaces=true</tt> an
May be disabled on <a href="http://localhost:7657/config.jsp">config.jsp</a>.
</i></li>
<li><b>7654:</b> I2P Client Protocol port, used by client apps.
<i>May be changed with the advanced configuration option</i> <tt>i2cp.port</tt>
<i>May be changed to a different port on
<a href="http://localhost:7657/configclients.jsp">configclients.jsp</a>
but this is not recommended.
May be changed to bind to all interfaces with the advanced configuration option
<tt>i2cp.tcp.bindAllInterfaces=true</tt>.
May be changed to bind to a specific interface with the advanced configuration option
<tt>i2cp.hostname=1.2.3.4</tt>.
May be to bind to a different interface or all interfaces, or disabled, on
<a href="http://localhost:7657/configclients.jsp">configclients.jsp</a>.
</i></li>
<li><b>7655:</b> UDP for SAM bridge, a higher level socket API for clients
<i>Only opened when a SAM V3 client requests a UDP session.

2
www.i2p2/pages/how.html
View File

@ -5,7 +5,7 @@
<p>
Following is an index to the technical documentation for I2P.
This information was updated in August 2010 and is accurate for router version 0.8.
This information was updated in January 2011 and is accurate for router version 0.8.3.
</p><p>
This index is ordered from the highest to lowest layers.
The higher layers are for "clients" or applications;

12
www.i2p2/pages/how_cryptography.html
View File

@ -2,7 +2,7 @@
{% block title %}Low-level Cryptography Details{% endblock %}
{% block content %}
<p>
Updated August 2010, current as of router version 0.8
Updated January 2011, current as of router version 0.8.3
<p>
This page specifies the low-level details of the cryptography in I2P.
<p>
@ -54,8 +54,10 @@ The unencrypted ElGamal contains:
</PRE>
<p>
The H(data) is the SHA256 of the data that is encrypted in the ElGamal block,
and is preceded by a random nonzero byte. The data encrypted in the block
may be up to 222 bytes long.
and is preceded by a nonzero byte.
This byte could be random, but as implemented it is always 0xFF.
It could possibly be used for flags in the future.
The data encrypted in the block may be up to 222 bytes long.
As the encrypted data may contain a substantial number of zeros if the
cleartext is smaller than 222 bytes, it is recommended that higher layers pad
the cleartext to 222 bytes with random data.
@ -120,7 +122,7 @@ or as a hexadecimal value:
Using 2 as the generator.
<h3>Short Exponent</h3>
While the standard exponent size is 2048 bits (256 bytes) and the I2P
<a href="common_data_structures.html#type_PrivateKey">PrivateKey</a>
<a href="common_structures_spec.html#type_PrivateKey">PrivateKey</a>
is a full 256 bytes,
we use the short exponent size of 226 bits (28.25 bytes).
This should be safe for use with the Oakley primes,
@ -139,7 +141,7 @@ Koshiba &amp; Kurosawa: Short Exponent Diffie-Hellman Problems</a> (PKC 2004, LN
(full text on google books)</a>
apparently supports this, according to
<a href="http://groups.google.com/group/sci.crypt/browse_thread/thread/1855a5efa7416677/339fa2f945cc9ba0#339fa2f945cc9ba0">this sci.crypt thread</a>.
The remainder of the PublicKey is padded with zeroes.
The remainder of the PrivateKey is padded with zeroes.
<H4>Obsolescence</H4>
<p>

10
www.i2p2/pages/i2cp.html
View File

@ -1,7 +1,7 @@
{% extends "_layout.html" %}
{% block title %}I2CP{% endblock %}
{% block content %}
Updated December 2010, current as of router version 0.8.2
Updated January 2011, current as of router version 0.8.3
<p>The I2P Client Protocol (I2CP) exposes a strong separation of concerns between
the router and any client that wishes to communicate over the network. It enables
@ -110,8 +110,10 @@ a <a href="i2cp_spec.html#type_SessionConfig">SessionConfig</a> contained in a <
<tr><td>i2cp.messageReliability <td>&nbsp;<td>BestEffort, Guaranteed, None<td>BestEffort<td>Guaranteed is disabled;
None implemented in 0.8.1; the streaming lib default is None as of 0.8.1
<tr><td>explicitPeers<td>&nbsp;<td>&nbsp;<td>null<td>Comma-separated list of Base 64 Hashes of peers to build tunnels through; for debugging only
<tr><td>i2cp.username<td>string<td>&nbsp;<td>&nbsp;<td>For authorization, if required by the router (since 0.8.2)
<tr><td>i2cp.password<td>string<td>&nbsp;<td>&nbsp;<td>For authorization, if required by the router (since 0.8.2)
<tr><td>i2cp.username<td>string<td>&nbsp;<td>&nbsp;<td>For authorization, if required by the router (since 0.8.2).
If the client is running in the same JVM as a router, this option is not required.
<tr><td>i2cp.password<td>string<td>&nbsp;<td>&nbsp;<td>For authorization, if required by the router (since 0.8.2).
If the client is running in the same JVM as a router, this option is not required.
</table>
<p>
Note: Large quantity, length, or variance settings may cause significant performance or reliability problems.
@ -131,6 +133,8 @@ The streaming lib should also pass these options through to I2CP.
If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally.
<tr><td>i2cp.tcp.port <td>&nbsp;<td>&nbsp;<td>1-65535<td>7654<td>Router I2CP port.
If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally.
<tr><td>i2cp.SSL<td>0.8.3<td>true, false<td>&nbsp;<td>false<td>Connect to the router using SSL.
If the client is running in the same JVM as a router, this option is ignored, and the client connects to that router internally.
<tr><td>i2cp.gzip<td>0.6.5<td>true, false <td>&nbsp;<td>true<td>Gzip outbound data
<tr><td>i2cp.reduceOnIdle<td>0.7.1<td>true, false <td>&nbsp;<td>false<td>Reduce tunnel quantity when idle
<tr><td>i2cp.closeOnIdle<td>0.7.1<td>true, false <td>&nbsp;<td>false<td>Close I2P session when idle