4 ms·
Is there a reason you couldn't use TCP/TLS to establish a shared secret, and then just encrypt all your packets with that?
by hamandcheese 10y ago
Is there a reason you couldn't use TCP/TLS to establish a shared secret, and then just encrypt all your packets with that?
- rusk 10y agoGosh .. I eh .. I guess I was just given this RFC to implement [0] I'm not sure of the reasoning specifically for doing it this way. But kind of related to your point, TTLS does in fact use the "cryptographic material" derived as part of session establishment to derive a shared secret for hashing in CHAP, MS-CHAP and MS-CHAP-v2! [1] The nifty thing about that is it "binds" the ensuing authentication process to the actual TLS session. With MS-CHAP-v2 it also provides for mutual authentication without either party ever having to exchange sensitive info (neither client nor server ever has to know the password). This was actually a real pain to do with Open SSL as that information wasn't readily available with the standard API. I had to implement some horrific cludge to get the necessary info nested within 3 layers of structs. [0] https://tools.ietf.org/html/rfc5281 https://tools.ietf.org/html/rfc5281 [1] https://tools.ietf.org/html/rfc5281#section-8 https://tools.ietf.org/html/rfc5281#section-8