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

forgot to update the processing xor

Browse Source
This commit is contained in:
jrandom
2005-01-15 03:53:13 +00:00
committed by zzz
parent 1a15d3bb55
commit 75a18debcb
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
router/doc/tunnel.html
View File

@ -1,4 +1,4 @@
<code>$Id: tunnel.html,v 1.5 2005/01/14 17:43:44 jrandom Exp $</code> <code>$Id: tunnel.html,v 1.6 2005/01/14 19:06:40 jrandom Exp $</code>
<pre> <pre>
1) <a href="#tunnel.overview">Tunnel overview</a> 1) <a href="#tunnel.overview">Tunnel overview</a>
2) <a href="#tunnel.operation">Tunnel operation</a> 2) <a href="#tunnel.operation">Tunnel operation</a>
@ -264,9 +264,9 @@ peer who is the first hop (usually the peer1.recv row) and forward that entirely
tunnel key using AES256 in CTR mode with the first 16 bytes as the IV. They then tunnel key using AES256 in CTR mode with the first 16 bytes as the IV. They then
calculate the hash of what they see as the payload (bytes 16 through $size-288) and calculate the hash of what they see as the payload (bytes 16 through $size-288) and
search for that hash within the decrypted checksum block. If no match is found, the search for that hash within the decrypted checksum block. If no match is found, the
message is discarded. Otherwise, the IV is updated by decrypting it and replacing it message is discarded. Otherwise, the IV is updated by decrypting it, XORing that value
with the first 16 bytes of its hash. The resulting message is then forwarded on to with the IV_WHITENER, and replacing it with the first 16 bytes of its hash. The
the next peer for processing.</p> resulting message is then forwarded on to the next peer for processing.</p>
<h3>2.4) <a name="tunnel.endpoint">Endpoint processing</a></h3> <h3>2.4) <a name="tunnel.endpoint">Endpoint processing</a></h3>