6 ms·
This is Noise NK, possibly with differences in the hashing details which I did not check: https://noiseprotocol.org/noise.html#interactive-handshake-patterns-f
by crotchfire 2y ago
This is Noise NK, possibly with differences in the hashing details which I did not check:
https://noiseprotocol.org/noise.html#interactive-handshake-patterns-fundamental https://noiseprotocol.org/noise.html#interactive-handshake-p...
I encourage you to use their hashing details. They're battle-tested.
Wireguard uses Noise IK, which is NK plus a static public key for the initiator which is encrypted to the agreed-upon-session-key without adding additional round trips. Your protocol and Noise NK omit the parts related to the initiator's static public key, because it has none.
- cobratbq 2y agoI will have a look. I checked quickly already, so if I understand the notation, I also leave out the last transaction. (2 messages vs 3 messages) Presumably because the authentication is one-sided. Will investigate further.
- crotchfire 2y agoYou have misunderstood the notation; Noise NK is 2 messages, one round trip. Exchanges above the dotted line are one-time key distributions; see this link: https://archive.li/bU5Me#selection-3667.0-3671.36 https://archive.li/bU5Me#selection-3667.0-3671.36
- cobratbq 2y agoYeah, sorry, I realized that later. I forgot I posted the comment already.