They published a brand new TLS-like protocol in a top academic security conference without a proof of security.
-
-
-
Right, the issue he has is with
@trevp__ 's NoiseIK -- https://noiseprotocol.org/noise.pdf Notably the only security analysis done on other aspects of the WireGuard protocol -- such as the Cookies and defense-in-depth design -- has been in the original NDSS paper.1 reply 0 retweets 0 likes -
Replying to @EdgeSecurity @tqbf and
I don’t understand why “NoiseIK May have the same weakness” is making this better.
2 replies 0 retweets 1 like -
Replying to @matthew_d_green @tqbf and
"Making it better?" It sounds to me like you're just thoroughly confused. WireGuard implements NoiseIK. The Dowling/Paterson paper and the Tamarin paper analyze NoiseIK. That's the topic of our conversation here. "Same weakness": also, there's no weakness even found here, so...
1 reply 0 retweets 0 likes -
Replying to @EdgeSecurity @tqbf and
Due respect, I’m just responding to Thomas’s comment. No need to be rude about it.
1 reply 0 retweets 1 like -
Replying to @matthew_d_green @tqbf and
No disrespect intended. Trying to clarify what appears to be a misunderstanding about what part of WireGuard is being analyzed in these papers. The key exchange is (with the three horizontal lines) NoiseIK. That's all.
1 reply 0 retweets 0 likes -
Replying to @EdgeSecurity @tqbf and
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.
2 replies 0 retweets 1 like -
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
Noise specifies both the handshake and the transport ("record").
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.