63006a913b
Although Chromium actually uses SSL_(get_)state as part of its fallback reason heuristic, that function really should go in the deprecated bucket. I kept SSL_state_string_long since having a human-readable string is probably useful for logging. SSL_set_SSL_CTX was only half-documented as the behavior of this function is very weird. This warrants further investigation and rethinking. SSL_set_shutdown is absurd. I added an assert to trip up clearing bits and set it to a bitwise OR since clearing bits may mess up the state machine. Otherwise there's enough consumers and it's not quite the same as SSL_CTX_set_quiet_shutdown that I've left it alone for now. Change-Id: Ie35850529373a5a795f6eb04222668ff76d84aaa Reviewed-on: https://boringssl-review.googlesource.com/6312 Reviewed-by: Adam Langley <alangley@gmail.com> |
||
---|---|---|
.. | ||
openssl |