summaryrefslogtreecommitdiff
path: root/src/lib/libssl/tls13_key_schedule.c
diff options
context:
space:
mode:
authorjsing <>2020-11-11 18:20:10 +0000
committerjsing <>2020-11-11 18:20:10 +0000
commit5bc4eba7ef5295b28908fc64844ded7577e36d50 (patch)
tree9db60455c379dcbf4e84964fd07b8ba3fe0ab8a9 /src/lib/libssl/tls13_key_schedule.c
parent6872c16fec8622b4dc934604415b6d1b065724fb (diff)
downloadopenbsd-5bc4eba7ef5295b28908fc64844ded7577e36d50.tar.gz
openbsd-5bc4eba7ef5295b28908fc64844ded7577e36d50.tar.bz2
openbsd-5bc4eba7ef5295b28908fc64844ded7577e36d50.zip
Implement auto chain for the TLSv1.3 server.
Apparently OpenLDAP relies on this craziness to provide intermediates, rather than specifying the chain directly like a normal TLS server would. Issue noted by sthen@ and Bernard Spil, who both also tested this diff. ok tb@
Diffstat (limited to 'src/lib/libssl/tls13_key_schedule.c')
0 files changed, 0 insertions, 0 deletions