summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/recallocarray.c
diff options
context:
space:
mode:
authorjsing <>2025-03-12 14:03:55 +0000
committerjsing <>2025-03-12 14:03:55 +0000
commitcc5a28ea6d2a0de9bcd56f07684bdc53cdfd10af (patch)
tree115a09cea80866af43519a40dfdd3e9409e4cc96 /src/lib/libc/stdlib/recallocarray.c
parent93373bbf82b95dab0336951cf191b5fecde0597c (diff)
downloadopenbsd-cc5a28ea6d2a0de9bcd56f07684bdc53cdfd10af.tar.gz
openbsd-cc5a28ea6d2a0de9bcd56f07684bdc53cdfd10af.tar.bz2
openbsd-cc5a28ea6d2a0de9bcd56f07684bdc53cdfd10af.zip
Provide SSL_OP_NO_RENEGOTIATION and SSL_OP_ALLOW_CLIENT_RENEGOTIATION.
In January 2017 we added SSL_OP_NO_CLIENT_RENEGOTIATION, which results in a SSL_AD_NO_RENEGOTIATION fatal alert if a ClientHello message is seen on an active connection (client initiated renegotation). Then in May 2017 OpenSSL added SSL_OP_NO_RENEGOTIATION, which results in a SSL_AD_NO_RENEGOTIATION warning alert if a server receives a ClientHello on an active connection (client initiated renegotation), or a client receives a HelloRequest (server requested renegotation). This option also causes calls to SSL_renegotiate() and SSL_renegotiate_abbreviated() to fail. Then in 2021, OpenSSL also added SSL_OP_ALLOW_CLIENT_RENEGOTIATION, which trumps SSL_OP_NO_RENEGOTIATION but only for incoming ClientHello messages (apparently unsetting SSL_OP_NO_RENEGOTIATION is too hard). Provide SSL_OP_NO_RENEGOTIATION and SSL_OP_ALLOW_CLIENT_RENEGOTIATION, primarily to make life easier for ports. If SSL_OP_NO_CLIENT_RENEGOTIATION is set it will take precedence and render SSL_OP_ALLOW_CLIENT_RENEGOTIATION ineffective. The rest of the behaviour should match OpenSSL, with the exception of ClientHellos triggering fatal alerts instead of warnings. ok tb@
Diffstat (limited to 'src/lib/libc/stdlib/recallocarray.c')
0 files changed, 0 insertions, 0 deletions