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

prop 144 updates part 2

Browse Source
This commit is contained in:
zzz
2019-09-19 14:58:43 +00:00
parent 90ab12894e
commit b7ca90ef95
1 changed files with 14 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
i2p2www/spec/proposals/144-ecies-x25519-aead-ratchet.rst
View File

@ -1217,7 +1217,6 @@ Optional blocks can have multiple I2NP blocks, but only a single padding block.
If present, the padding block must be the final block. If present, the padding block must be the final block.
KDF for Payload Section Encrypted Contents
KDF for Ephemeral Key Section Encrypted Contents KDF for Ephemeral Key Section Encrypted Contents
```````````````````````````````````````````````` ````````````````````````````````````````````````
@ -1281,12 +1280,23 @@ KDF for Ephemeral Key Section Encrypted Contents
{% endhighlight %} {% endhighlight %}
KDF for Payload Section Encrypted Contents
``````````````````````````````````````````
TODO basically like the first Existing Session message,
post-split.
.. raw:: html
{% highlight lang='text' %}
TODO
{% endhighlight %}
Notes Notes
----- -----
Bob must include the matching session ID in the reply Ephemeral Key Section for Alice to
properly decrypt and bind the reply inbound session with the original outbound session.
Multiple NSR messages may be sent in reply, each with unique ephemeral keys, depending on the size of the response. Multiple NSR messages may be sent in reply, each with unique ephemeral keys, depending on the size of the response.
Alice and Bob are required to use new ephemeral keys for every NS and NSR message. Alice and Bob are required to use new ephemeral keys for every NS and NSR message.