commit 7d0092c19a6c97b110a781bf18a154ba7651b5ea parent 77c3bb314d9510a06641a1afc27d699103782a61 Author: Julius Bünger <buenger@mytum.de> Date: Tue, 29 Oct 2024 15:10:25 +0100 cong: more details on network generation id Diffstat:
| M | developers/apis/cong.rst | | | 8 | ++++++++ |
1 file changed, 8 insertions(+), 0 deletions(-)
diff --git a/developers/apis/cong.rst b/developers/apis/cong.rst @@ -480,6 +480,14 @@ way) can be identified and dequeued. It is important to manage the network generation id as close to the communicators as possible to be able to stop the actual outgoing messages as quick as possible. +To be more precise, the communication via open channels should not cease when +the new peer id is available, but already when there's a change to the +addresses in use. This means there is a small window, until the new peer id is +generated, in which the peer is without peer id and thus without means to +communicate. This might open a new attack window by trying to change the +addresses of a peer via for example opening and closing wifi hotspots and +sending out new addresses via dhcp. + .. 64 bit: similar size to pid/hash