summaryrefslogtreecommitdiff
path: root/src/regress/lib/libssl/unit/tls_ext_alpn.c
diff options
context:
space:
mode:
authorjsing <>2019-01-18 00:54:42 +0000
committerjsing <>2019-01-18 00:54:42 +0000
commit9ef012160f94ffb22c839c82671d1f434a37474d (patch)
treebcaae6c0e0f49e2bff1aa790059cf07ac8b504e5 /src/regress/lib/libssl/unit/tls_ext_alpn.c
parent0a9d08c2680e23167a32b6bfb19d558a910b8ec1 (diff)
downloadopenbsd-9ef012160f94ffb22c839c82671d1f434a37474d.tar.gz
openbsd-9ef012160f94ffb22c839c82671d1f434a37474d.tar.bz2
openbsd-9ef012160f94ffb22c839c82671d1f434a37474d.zip
Rename TLS extension handling to use less "hello".
When the TLS extension code was rewritten, TLS extensions could only exist in ClientHello and ServerHello messages - as such, they were named in pairs of *_clienthello_{needs,build} which would be called by the client and *_clienthello_parse. Likewise for *_serverhello_{needs,build} which would be called by a server and *_serverhello_parse, which would be called by a client. Enter TLSv1.3 - TLS extensions can now exist in one of seven messages, with only certain types being allowed to appear in each, meaning the naming scheme no longer works. Instead, rename them to indicate the caller rather than the message type - this effectively means: clienthello_needs -> client_needs clienthello_build -> client_build clienthello_parse -> server_parse serverhello_needs -> server_needs serverhello_build -> server_build serverhello_parse -> client_parse ok beck@ tb@
Diffstat (limited to 'src/regress/lib/libssl/unit/tls_ext_alpn.c')
0 files changed, 0 insertions, 0 deletions