diff options
author | jsing <> | 2019-01-18 00:54:42 +0000 |
---|---|---|
committer | jsing <> | 2019-01-18 00:54:42 +0000 |
commit | 66af95e693522ba3868191014eaca1fa0a95176d (patch) | |
tree | bcaae6c0e0f49e2bff1aa790059cf07ac8b504e5 /src/regress/lib | |
parent | 154e80a0b5a0c3c4a9d3390a220e96f0f8c36aab (diff) | |
download | openbsd-66af95e693522ba3868191014eaca1fa0a95176d.tar.gz openbsd-66af95e693522ba3868191014eaca1fa0a95176d.tar.bz2 openbsd-66af95e693522ba3868191014eaca1fa0a95176d.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')
0 files changed, 0 insertions, 0 deletions