I looked at the paper as it is. I don’t know how much you changed from NoiseIK. If it’s the same as NoiseIK than that seems like two issues not one.
-
-
Replying to @matthew_d_green @EdgeSecurity and
A month ago I wrote an HN comment that suggested that Wireguard was distinguishable from Noise and Trevor chided me for it. The Wireguard paper itself says: the handshake is NoiseIK.
1 reply 0 retweets 2 likes -
Replying to @tqbf @EdgeSecurity and
But the problem here is the way the handshake interacts with the record protocol.
2 replies 0 retweets 2 likes -
Replying to @matthew_d_green @EdgeSecurity and
Right, it’s not meant to be modular. It’s meant to be streamlined, to simplify kernel C implementation. It’s an option Noise takes pain to offer.
2 replies 0 retweets 1 like -
Replying to @tqbf @matthew_d_green and
The Wireguard paper itself, written long before the RHUL thing, provides an explicit rationale for this choice; it’s one of their more interesting rationales.
1 reply 0 retweets 0 likes -
Replying to @tqbf @EdgeSecurity and
I’m actually trying to find where I’m S5 this is.
1 reply 0 retweets 0 likes -
Replying to @matthew_d_green @EdgeSecurity and
Am I misreading first graf of “Silence Is a Virtue”? Not unlikely that I am.
1 reply 0 retweets 0 likes -
Replying to @tqbf @EdgeSecurity and
It seems to indicate that the first message has special data that the later messages don’t have. Am I misreading this? It’s kind of vague. If it does have special data than put a key confirmation message into it.pic.twitter.com/UByjCydot7
2 replies 0 retweets 2 likes -
Replying to @matthew_d_green @tqbf and
If all transport messages are the same, I concede this is more complex.
1 reply 0 retweets 1 like -
Replying to @matthew_d_green @tqbf and
PS I’m referring to the sentence that includes “A 12 byte...is included in the first message.”
1 reply 0 retweets 1 like
Yes, I know. That 12 byte string is simply the "payload" part of the typical I-->R NoiseIK message. If you scroll down to the packet descriptions in the paper, you'll see how it's composed. Or checkout https://noiseprotocol.org/noise.pdf for the general framework.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.