3 ms·
From that slack convo, I disagreed. DTLS specifies everything for UDP: what happens if you receive messages out of order? or if the datagram length is not enoug
by baby 10y ago
From that slack convo, I disagreed. DTLS specifies everything for UDP: what happens if you receive messages out of order? or if the datagram length is not enough for a message? or if you drop messages? or if someone actively MITM you (easy in UDP)? DTLS specifies all these things. Noise doesn't. It's up to you to find out a way to make it work for UDP. Not that Noise specifies how to implement it on top of TCP, but it's more straight-forward there.
I was also told that Wireguard uses Noise on top of UDP, so it would be interesting to see what they did there.
Another good point for Noise: if you're planning to implement a TLS-like protocol from scratch, I would go for Noise instead of TLS. It's just simpler, lighter and easy to customize to your own needs.
- zx2c4 10y agoIndeed DTLS is a "pipe", whereas pure Noise isn't, and pure Noise doesn't have any DoS protection, which DTLS does. But indeed DTLS is a mess for other reasons. For WireGuard I use Noise with stronger DoS resistance and anti replay measures than DTLS, custom tailored for being a layer 3 tunnel. Details here: https://www.wireguard.io/papers/wireguard.pdf https://www.wireguard.io/papers/wireguard.pdf
- problems 10y ago> if someone actively MITM you (easy in UDP) In what way is MITM easier in UDP than TCP? Assuming you use similar techniques to verify your connection, I can't see a difference.
- baby 10y agoYou don't need to do anything to pretend you are the source address. Whereas in TCP you need to guess some random seq number.