summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto
diff options
context:
space:
mode:
authorjsing <>2022-03-14 16:49:35 +0000
committerjsing <>2022-03-14 16:49:35 +0000
commitfb6d4ea1385d6b1032c9c040a2b756900f3afbb8 (patch)
treef36b60b7bdcf81c644d8d156a92e99f3582d41d0 /src/lib/libcrypto
parented6d95418f799a0e00e49deb2fe14e76912fb1d9 (diff)
downloadopenbsd-fb6d4ea1385d6b1032c9c040a2b756900f3afbb8.tar.gz
openbsd-fb6d4ea1385d6b1032c9c040a2b756900f3afbb8.tar.bz2
openbsd-fb6d4ea1385d6b1032c9c040a2b756900f3afbb8.zip
Factor out unexpected handshake message handling code in the legacy stack.
The TLS record layer has to be able to handle unexpected handshake messages that result when it has been asked to read application data. The way that this is currently done in the legacy stack is a layering violation - the record layer knows about DTLS/TLS handshake messages, parsing them and then deciding what action to take. This is further complicated by the need to handle handshake message fragments. For now, factor this code out with minimal changes - since it is a layering violation we have to retain separate code for DTLS and TLS. ok beck@ inoguchi@ tb@
Diffstat (limited to 'src/lib/libcrypto')
0 files changed, 0 insertions, 0 deletions