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

Add Prop. 157 messages to ECIES tunnel spec

Browse Source
This commit is contained in:
zzz
2021-07-31 09:39:52 -04:00
parent f6fa065364
commit fb085e6cca
3 changed files with 345 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
i2p2www/spec/proposals/157-new-tbm.rst
View File

@@ -36,7 +36,7 @@ single tunnel message, the reverse path would be three times more efficient.
This proposal defines new request and reply records and new Build Request and Build Reply messages.
The tunnel creator and all hops in the created tunnel must ECIES-X25519, and at least version TBD.
The tunnel creator and all hops in the created tunnel must ECIES-X25519, and at least version 0.9.51.
This proposal will not be useful until a majority of the routers in the network are ECIES-X25519.
This is expected to happen by year-end 2021.
@@ -470,8 +470,8 @@ to derive following keys: reply key, AES layer key, AES IV key and garlic reply
Reply key:
Unlike long records we can't use left part of ck for reply key, because it's not last and will be used later.
Reply key is use to encypt reply that record using AEAD/Chaha20/Poly1305 and Chacha20 to reply other records.
Both use the same key, nonce is record's position in the message starring from 0.
Reply key is used to encypt reply that record using AEAD/Chaha20/Poly1305 and Chacha20 to reply other records.
Both use the same key, nonce is record's position in the message starting from 0.
.. raw:: html