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

merge of '3ba04cbd5e2470c5f12be392c0e59f4d498933bd'

Browse Source 
and 'cc71d90929d66504586434ddbdeea3828f3239bf'
This commit is contained in:
zab2
2018-11-21 14:54:37 +00:00
parent aae6bbe9e7 6118a820cb
commit 0d2ccd6c06
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
i2p2www/spec/proposals/123-new-netdb-entries.rst
View File

@ -5,7 +5,7 @@ New netDB Entries
:author: zzz, orignal, str4d
:created: 2016-01-16
:thread: http://zzz.i2p/topics/2051
:lastupdated: 2018-11-12
:lastupdated: 2018-11-19
:status: Open
:supercedes: 110, 120, 121, 122
@ -488,8 +488,8 @@ Does NOT use the standard LS2 header specified above.
Published timestamp is the nonce
Do we need HMAC or ChaCha only? Probably don't need HMAC, everything is signed.
KDF TBD. Used blinded public key. Uses cookie also if per-client.
When decrypted, the data for type 2 or 4, including the header,
but without the timestamp and expires fields?
When decrypted, contains a type byte: 3 (LS2) or 7 (Meta LS2),
followed by the data, including the header and signature, for that type.
- Signature (by blinded public key, length as implied by blinded sig type)
The signature is of everything above.
@ -517,6 +517,8 @@ Notes
- Floodfills may limit the max size to a reasonable value to prevent abuse.
- After decryption, several checks should be made, including that
the inner timestamp and expiration match those at the top level.