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

ntcp2 notes
Some checks failed
/ repo-sync (push) Failing after 7s
Details

Browse Source
This commit is contained in:
zzz
2025-05-03 10:23:01 -04:00
parent ab4b805645
commit 835d94407f
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
i2p2www/spec/ntcp2.rst
View File

@@ -3,7 +3,7 @@ NTCP 2
====== ======
.. meta:: .. meta::
:category: Transports :category: Transports
:lastupdated: 2025-04 :lastupdated: 2025-05
:accuratefor: 0.9.66 :accuratefor: 0.9.66
.. contents:: .. contents::
@@ -574,6 +574,10 @@ Notes
set a random timeout (range TBD) and then read a random number of bytes (range TBD), set a random timeout (range TBD) and then read a random number of bytes (range TBD),
before closing the socket. before closing the socket.
- Bob may do a fast MSB check for a valid key (X[31] & 0x80 == 0) before
attempting decryption. If the high bit is set, implement probing resistance
as for AEAD failures.
- DoS Mitigation: DH is a relatively expensive operation. As with the previous NTCP protocol, - DoS Mitigation: DH is a relatively expensive operation. As with the previous NTCP protocol,
routers should take all necessary measures to prevent CPU or connection exhaustion. routers should take all necessary measures to prevent CPU or connection exhaustion.
Place limits on maximum active connections and maximum connection setups in progress. Place limits on maximum active connections and maximum connection setups in progress.