Thomas Eizinger f5425ac8e4 fix(snownet): fail connection on handshake decryption errors (#9850) ...

As per the WireGuard paper, `boringtun` tries to handshake with the
remote peer for 90s before it gives up. This timeout is important
because when a session is discarded due to e.g. missing replies,
WireGuard attempts to handshake a new session. Without this timeout, we
would then try to handshake a session forever.

Unfortunately, `boringtun` does not distinguish a missing handshake
response from a bad one. Decryption errors whilst decoding a handshake
response are simply passed up to the upper layer, in our case `snownet`.

I am not sure how we can actually fail to decrypt a handshake but the
pattern we are seeing in customer logs is that this happens over and
over again, so there is no point in having `boringtun` retry the
handshake. Therefore, we immediately fail the connection when this
happens.

Failed connections are immediately removed, triggering the client send a
new connection-intent to the portal. Such a new connection intent will
then sync-up the state between Client and Gateway so both of them use
the most recent public key.

Resolves: #9845

2025-07-14 13:22:23 +00:00

..

src

fix(snownet): fail connection on handshake decryption errors (#9850)

2025-07-14 13:22:23 +00:00

Cargo.toml

feat(gateway): allow exporting metrics to an OTEL collector (#9838)

2025-07-14 03:54:38 +00:00