diff --git a/www.i2p2/pages/faq.html b/www.i2p2/pages/faq.html index 8abdbb67..0dd1ddc7 100644 --- a/www.i2p2/pages/faq.html +++ b/www.i2p2/pages/faq.html @@ -464,6 +464,10 @@ router advanced configuration option i2cp.tcp.bindAllInterfaces=true an 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. +
  • 4445: HTTPS proxy + 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. +
  • 6668: IRC proxy 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 i2cp.tcp.bindAllInterfaces=true an May be disabled on config.jsp.
  • 7654: I2P Client Protocol port, used by client apps. - May be changed with the advanced configuration option i2cp.port + May be changed to a different port on + configclients.jsp but this is not recommended. - May be changed to bind to all interfaces with the advanced configuration option - i2cp.tcp.bindAllInterfaces=true. - May be changed to bind to a specific interface with the advanced configuration option - i2cp.hostname=1.2.3.4. + May be to bind to a different interface or all interfaces, or disabled, on + configclients.jsp.
  • 7655: UDP for SAM bridge, a higher level socket API for clients Only opened when a SAM V3 client requests a UDP session. diff --git a/www.i2p2/pages/how.html b/www.i2p2/pages/how.html index 047ce7ce..c8c05e27 100644 --- a/www.i2p2/pages/how.html +++ b/www.i2p2/pages/how.html @@ -5,7 +5,7 @@

    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.

    This index is ordered from the highest to lowest layers. The higher layers are for "clients" or applications; diff --git a/www.i2p2/pages/how_cryptography.html b/www.i2p2/pages/how_cryptography.html index 09a29da9..0ab3f628 100644 --- a/www.i2p2/pages/how_cryptography.html +++ b/www.i2p2/pages/how_cryptography.html @@ -2,7 +2,7 @@ {% block title %}Low-level Cryptography Details{% endblock %} {% block content %}

    -Updated August 2010, current as of router version 0.8 +Updated January 2011, current as of router version 0.8.3

    This page specifies the low-level details of the cryptography in I2P.

    @@ -54,8 +54,10 @@ The unencrypted ElGamal contains:

    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.

    Short Exponent

    While the standard exponent size is 2048 bits (256 bytes) and the I2P -PrivateKey +PrivateKey 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 & Kurosawa: Short Exponent Diffie-Hellman Problems (PKC 2004, LN (full text on google books) apparently supports this, according to this sci.crypt thread. -The remainder of the PublicKey is padded with zeroes. +The remainder of the PrivateKey is padded with zeroes.

    Obsolescence

    diff --git a/www.i2p2/pages/i2cp.html b/www.i2p2/pages/i2cp.html index b5cd6c00..bc096a6d 100644 --- a/www.i2p2/pages/i2cp.html +++ b/www.i2p2/pages/i2cp.html @@ -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

    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 SessionConfig contained in a < i2cp.messageReliability  BestEffort, Guaranteed, NoneBestEffortGuaranteed is disabled; None implemented in 0.8.1; the streaming lib default is None as of 0.8.1 explicitPeers  nullComma-separated list of Base 64 Hashes of peers to build tunnels through; for debugging only -i2cp.usernamestring  For authorization, if required by the router (since 0.8.2) -i2cp.passwordstring  For authorization, if required by the router (since 0.8.2) +i2cp.usernamestring  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. +i2cp.passwordstring  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.

    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. i2cp.tcp.port   1-655357654Router 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. +i2cp.SSL0.8.3true, false falseConnect 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. i2cp.gzip0.6.5true, false  trueGzip outbound data i2cp.reduceOnIdle0.7.1true, false  falseReduce tunnel quantity when idle i2cp.closeOnIdle0.7.1true, false  falseClose I2P session when idle