mirror of
https://github.com/tailscale/tailscale.git
synced 2026-11-20 08:41:19 -08:00
ee627ef16eeaab3d989b8fae66854ec52c5eaf2a
Tailscale's wireguard-go has a hybrid handshake, Noise_IKhfs+psk2_25519+MLKEM768, which both peers must agree to use, with no fallback to the classic one. A kernel-mode node without it would be cut off from any peer that asked for it. The initiation now may carry an ephemeral ML-KEM-768 encapsulation key, sealed under the es key (with the static key then using nonce 1), and the response a ciphertext for it, sealed under the ee key, whose shared secret is mixed into the chaining key before se. That's per peer, with the new TSWGPEER_F_HYBRID flag. Hybrid retries carry wireguard-go's retry bit (bit 31 of the type), which we accept, set and echo, and which the socket's message classifier now allows. Linux has no ML-KEM, and its SHA-3 is too new for the kernels we build for, so src/mlkem.c is a FIPS 203 ML-KEM-768 with its own Keccak. tests/mlkem checks it against Go's crypto/mlkem: the same keys from the same seeds, each decapsulating the other's ciphertexts, and the same implicit rejection. The natlab tests in tailscale.com check the handshake against wireguard-go, in both roles. Updates #426 Signed-off-by: Brad Fitzpatrick <[email protected]> Change-Id: Ic524483d6cd27d36900a730553e1b21e4530c399
Languages
Go
96.5%
C
1.2%
TypeScript
0.8%
Shell
0.5%
Swift
0.3%
Other
0.3%