kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify that tunnel IDs may not be zero

Browse Source
This commit is contained in:
zzz
2018-03-07 17:59:24 +00:00
parent cca11097c3
commit 7f662e9d3a
2 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
i2p2www/spec/i2np.rst
View File

@@ -3,8 +3,8 @@ I2NP Specification
==================
.. meta::
:category: Protocols
:lastupdated: January 2017
:accuratefor: 0.9.28
:lastupdated: March 2018
:accuratefor: 0.9.34
.. contents::
@@ -308,12 +308,14 @@ Cleartext:
receive_tunnel :: `TunnelId`
length -> 4 bytes
nonzero
our_ident :: `Hash`
length -> 32 bytes
next_tunnel :: `TunnelId`
length -> 4 bytes
nonzero
next_ident :: `Hash`
length -> 32 bytes

10
i2p2www/spec/tunnel-creation.rst
View File

@@ -3,8 +3,8 @@ Tunnel Creation Specification
=============================
.. meta::
:category: Design
:lastupdated: January 2016
:accuratefor: 0.9.24
:lastupdated: March 2018
:accuratefor: 0.9.34
.. contents::
@@ -58,9 +58,9 @@ Also specified in the I2NP Specification [BRR]_.
Cleartext of the record, visible only to the hop being asked::
bytes 0-3: tunnel ID to receive messages as
bytes 0-3: tunnel ID to receive messages as, nonzero
bytes 4-35: local router identity hash
bytes 36-39: next tunnel ID
bytes 36-39: next tunnel ID, nonzero
bytes 40-71: next router identity hash
bytes 72-103: AES-256 tunnel layer key
bytes 104-135: AES-256 tunnel IV key
@@ -95,7 +95,7 @@ set, the hop will be an intermediate participant. Both cannot be set at once.
Request Record Creation
```````````````````````
Every hop gets a random Tunnel ID.
Every hop gets a random Tunnel ID, nonzero.
The current and next-hop Tunnel IDs are filled in.
Every record gets a random tunnel IV key, reply IV, layer key, and reply key.