4 ms·
DTLS is probably one of your best options. Protecting UDP is hard. It more or less requires you to implement "all" the features DTLS has (like sequence numbers)
by Bino 13y ago
DTLS is probably one of your best options. Protecting UDP is hard. It more or less requires you to implement "all" the features DTLS has (like sequence numbers). Depending on the application, one could argue that your protocol maybe shouldn't implements encryption (wouldn't be the first protocol not to do so). And it should be left to the user to protect the traffic in their network. In some sense it's better not to try (and be open about it) than to fail.
- pjungwir 13y agoThanks for your opinion! I sort of agree. I'm trying to understand the DTLS RFC, and it sounds like DTLS (and maybe anything else that avoids replay attacks) requires you to set up a "conversation" initially, which sort of reduces the appeal of UDP. So lifting that work out of the protocol into an outside context, which the user could set up or not, might be best.