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

prop. 154 minor cleanups

Browse Source
This commit is contained in:
zzz
2020-03-23 14:38:09 +00:00
parent 5c084e794a
commit 7f82714283
1 changed files with 18 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
i2p2www/spec/proposals/154-ecies-lookups.rst
View File

@@ -11,8 +11,11 @@ Database Lookups from ECIES Destinations
.. contents:: .. contents::
Overview
========
Definitions Definitions
=========== -----------
- AEAD: ChaCha20/Poly1305 - AEAD: ChaCha20/Poly1305
- DLM: I2NP Database Lookup Message - DLM: I2NP Database Lookup Message
@@ -26,8 +29,8 @@ Definitions
- reply: I2NP DSM or DSRM - reply: I2NP DSM or DSRM
Overview Summary
======== -------
When sending a DLM for a LS to a floodfill, the DLM generally specifies When sending a DLM for a LS to a floodfill, the DLM generally specifies
that the reply be tagged, AES encrypted, and sent down a tunnel to the destination. that the reply be tagged, AES encrypted, and sent down a tunnel to the destination.
@@ -47,7 +50,7 @@ This proposal documents a new option in the DLM to request ECIES-encrypted repli
Goals Goals
===== -----
- New flags for DLM when an encrypted reply is requested down a tunnel to a ECIES destination - New flags for DLM when an encrypted reply is requested down a tunnel to a ECIES destination
- For the reply, add forward secrecy and sender authentication resistant to - For the reply, add forward secrecy and sender authentication resistant to
@@ -56,7 +59,7 @@ Goals
- Minimize crypto overhead - Minimize crypto overhead
Non-Goals Non-Goals
========= ---------
- No change to the encryption or security properties of the lookup (DLM). - No change to the encryption or security properties of the lookup (DLM).
The lookup has forward secrecy for requester key compromise only. The lookup has forward secrecy for requester key compromise only.
@@ -129,7 +132,11 @@ Flag bits 4/1 From Dest To Router Reply DH? notes
ElG to ElG ElG to ElG
---------- ----------
Minor changes. ElG destination sends a lookup to a ElG router.
Minor changes to the specification to check for new bit 4.
No changes to the existing binary format.
Requester key generation (clarification): Requester key generation (clarification):
@@ -140,7 +147,7 @@ reply_key :: CSRNG(32) 32 bytes random data
reply_tags :: Each is CSRNG(32) 32 bytes random data reply_tags :: Each is CSRNG(32) 32 bytes random data
{% endhighlight %} {% endhighlight %}
Message format: Message format (add check for ECIESFlag):
.. raw:: html .. raw:: html
@@ -166,6 +173,8 @@ reply_key ::
ECIES to ElG ECIES to ElG
------------ ------------
ECIES destination sends a lookup to a ElG router.
The reply_key and reply_tags fields are redefined for an ECIES-encrypted reply. The reply_key and reply_tags fields are redefined for an ECIES-encrypted reply.
Requester key generation: Requester key generation:
@@ -227,6 +236,8 @@ tag :: 8 byte reply_tag
ECIES to ECIES ECIES to ECIES
-------------- --------------
ECIES destination sends a lookup to a ECIES router.
The lookup will use the "one time format" in [ECIES]_ The lookup will use the "one time format" in [ECIES]_
as the requester is anonymous. as the requester is anonymous.