We do not need that many responses with FindNodeFast, since the
reposes can be ordered by distance
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
* use unix time for ttl
* don't remove all entries on peer removal
* cleanup questionable tuple destructure
* ignore vscode
* fix endians decoding
* allow removing by peerId
* invalidate cache by peerId on remove
* update test
* improve tracing of message exchange
run e.g. as
```
nim c -r -d:debug -d:chronicles_enabled=on -d:chronicles_log_level=TRACE -d:chronicles_sinks=textlines[nocolors,stdout] tests/dht/test_providers.nim >err
```
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
* add debug on Handshake timeour
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
* queue messages during handshake and send later
If a handshake was already in progress, messages were dropped.
Instead of this, it is better to queue these and send as soon
as the handshake is finished and thus the encryption key is known.
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
* rename handshakeInProgress to keyexchangeInProgress
Handshake is also a name of a message, which makes previous
name less clear.
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
* keyexchangeInProgress: do not remove on handshake received
This is the wrong direction, not needed
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
* fix cross-connect key exchange
Since key exchange can be started both ways simultaneously, and
these might not get finalised with UDP transport, we can't be
sure what encryption key will be used by the other side:
- the one derived in the key-exchange started by us,
- the one derived in the key-exchange started by the other node.
To alleviate this issue, we store two decryption keys in each session.
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
---------
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
* encodeMessagePacket: expose haskey
encodeMessagePacket checks for session and behaves differently
based on that. Exposing this difference in behavior.
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
* improve tracing of message exchange
run e.g. as
```
nim c -r -d:debug -d:chronicles_enabled=on -d:chronicles_log_level=TRACE -d:chronicles_sinks=textlines[nocolors,stdout] tests/dht/test_providers.nim >err
```
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
* add debug on Handshake timeour
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
* queue messages during handshake and send later
If a handshake was already in progress, messages were dropped.
Instead of this, it is better to queue these and send as soon
as the handshake is finished and thus the encryption key is known.
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
* rename handshakeInProgress to keyexchangeInProgress
Handshake is also a name of a message, which makes previous
name less clear.
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
* keyexchangeInProgress: do not remove on handshake received
This is the wrong direction, not needed
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
---------
Signed-off-by: Csaba Kiraly <csaba.kiraly@gmail.com>
Updates all Status IM and Codex Storage deps to the latest except for nim-stint which is held back due to some compiler issue.
* fix nimble name
* don't override nimble
* update all deps
* import nimble.lock and fix urls
* don't forget nim
* bump to chronos with async notifications
* make encryption scheme explicit
* supress compiler noise
* make `nimble install` without `-d` work
* move `libp2p_pki_schemes=secp256k1` to config.nims
* fix include
Changes the CI to properly cache Nimble deps *including* Nim binaries.
* parallelize tests
* speed up tests
* cache whole nimble
* use nimble install without -d
* bump version
* new nimble cache
* fix github_env
* compare speed
* readd msys2
* don't need make for nimble
* ugh renames
Csaba Kiraly
Giuliano Mega
Dmitriy Ryajov
Csaba Kiraly
Jaremy Creechley
Slava
Ivan Yonchovski