From c8ca33bac163628524715ab25414b808b8d4448a Mon Sep 17 00:00:00 2001 From: zzz Date: Thu, 26 Aug 2010 14:10:37 +0000 Subject: [PATCH] tweaks --- www.i2p2/pages/common_structures_spec.html | 28 ++++++++++++++++++++-- www.i2p2/pages/how_cryptography.html | 3 +++ www.i2p2/pages/how_garlicrouting.html | 4 ++-- www.i2p2/pages/i2np_spec.html | 4 ++++ www.i2p2/pages/ntcp.html | 3 +++ www.i2p2/pages/performance.html | 10 ++------ 6 files changed, 40 insertions(+), 12 deletions(-) diff --git a/www.i2p2/pages/common_structures_spec.html b/www.i2p2/pages/common_structures_spec.html index 64795613..513b2ca2 100644 --- a/www.i2p2/pages/common_structures_spec.html +++ b/www.i2p2/pages/common_structures_spec.html @@ -4,7 +4,11 @@ Updated August 2010, current as of router version 0.8

Data types Specification

- This document describes some data types common to all I2P protocols, like I2NP, I2CP, NTCP, etc. + This document describes some data types common to all I2P protocols, like + I2NP, + I2CP, + SSU, + etc.

Integer

@@ -380,7 +384,7 @@ Total length: 387+ bytes | end_date | +----+----+----+----+----+----+----+----+ -tunnel_gw :: RouterIdentity +tunnel_gw :: RouterIdentity of the tunnel gateway length -> >= 387 bytes tunnel_id :: TunnelId @@ -391,6 +395,13 @@ end_date :: Date {% endfilter %} +

Notes

+ + +

Javadoc

LeaseSet

@@ -543,6 +554,15 @@ options :: Mapping {% endfilter %} +

Notes

+ + +

Javadoc

RouterInfo

@@ -640,4 +660,8 @@ The signature may be verified using the signing public key of the router_ident.

Javadoc

+ +

Delivery Instructions

+Defined in the Tunnel Message Specification. + {% endblock %} diff --git a/www.i2p2/pages/how_cryptography.html b/www.i2p2/pages/how_cryptography.html index 722ebcb1..2b63e6a8 100644 --- a/www.i2p2/pages/how_cryptography.html +++ b/www.i2p2/pages/how_cryptography.html @@ -277,6 +277,9 @@ Both transports use 256 byte (2048 bit) Diffie-Hellman key exchange using the same shared prime and generator as specified above for ElGamal, followed by symmetric AES encryption as described above. +This provides +perfect forward secrecy +on the transport links.

NTCP connections

diff --git a/www.i2p2/pages/how_garlicrouting.html b/www.i2p2/pages/how_garlicrouting.html index 54a18553..2984b2b6 100644 --- a/www.i2p2/pages/how_garlicrouting.html +++ b/www.i2p2/pages/how_garlicrouting.html @@ -107,8 +107,8 @@ exploiting transport latency/throughput tradeoffs, and branching data through re

Tunnel Building and Routing

-In I2P, tunnels are unidirectional, and we require two tunnels -(one outbound and one inbound) for end-to-end communication in each direction. +In I2P, tunnels are unidirectional. Each party builds two tunnels, +one for outbound and one for inbound traffic. Therefore, four tunnels are required for a single round-trip message and reply.

Tunnels are built, and then used, with layered encryption. diff --git a/www.i2p2/pages/i2np_spec.html b/www.i2p2/pages/i2np_spec.html index 94fc51c7..05ec6695 100644 --- a/www.i2p2/pages/i2np_spec.html +++ b/www.i2p2/pages/i2np_spec.html @@ -298,6 +298,10 @@ Certificate :: Always NULL in the current implementation (3 bytes total, all zer +

Delivery Instructions

+Defined in the Tunnel Message Specification. + +

Messages

diff --git a/www.i2p2/pages/ntcp.html b/www.i2p2/pages/ntcp.html index 4c2a8811..54008d93 100644 --- a/www.i2p2/pages/ntcp.html +++ b/www.i2p2/pages/ntcp.html @@ -424,6 +424,9 @@ to create a limited number of message sizes.
  • Memory utilization (including that of the kernel) for NTCP should be compared to that for SSU.
  • +Can the establishment messages be randomly padded somehow, to frustrate +identification of I2P traffic based on initial packet sizes? +
  • Review and possibly disable 'check connection'

    • diff --git a/www.i2p2/pages/performance.html b/www.i2p2/pages/performance.html index 22dd79e0..07eacb77 100644 --- a/www.i2p2/pages/performance.html +++ b/www.i2p2/pages/performance.html @@ -101,17 +101,11 @@ bandwidth, latency, and CPU usage.

    Full streaming protocol improvements