43341433a8
Suppress CT callbacks with aNULL or PSK ciphersuites that involve no certificates. Ditto when the certificate chain is validated via DANE-TA(2) or DANE-EE(3) TLSA records. Also skip SCT processing when the chain is fails verification. Move and consolidate CT callbacks from libcrypto to libssl. We also simplify the interface to SSL_{,CTX_}_enable_ct() which can specify either a permissive mode that just collects information or a strict mode that requires at least one valid SCT or else asks to abort the connection. Simplified SCT processing and options in s_client(1) which now has just a simple pair of "-noct" vs. "-ct" options, the latter enables the permissive callback so that we can complete the handshake and report all relevant information. When printing SCTs, print the validation status if set and not valid. Signed-off-by: Rob Percival <robpercival@google.com> Reviewed-by: Emilia Käsper <emilia@openssl.org> |
||
---|---|---|
.. | ||
README | ||
statem.c | ||
statem.h | ||
statem_clnt.c | ||
statem_dtls.c | ||
statem_lib.c | ||
statem_locl.h | ||
statem_srvr.c |
State Machine Design ==================== This file provides some guidance on the thinking behind the design of the state machine code to aid future maintenance. The state machine code replaces an older state machine present in OpenSSL versions 1.0.2 and below. The new state machine has the following objectives: - Remove duplication of state code between client and server - Remove duplication of state code between TLS and DTLS - Simplify transitions and bring the logic together in a single location so that it is easier to validate - Remove duplication of code between each of the message handling functions - Receive a message first and then work out whether that is a valid transition - not the other way around (the other way causes lots of issues where we are expecting one type of message next but actually get something else) - Separate message flow state from handshake state (in order to better understand each) - message flow state = when to flush buffers; handling restarts in the event of NBIO events; handling the common flow of steps for reading a message and the common flow of steps for writing a message etc - handshake state = what handshake message are we working on now - Control complexity: only the state machine can change state: keep all the state changes local to the state machine component The message flow state machine is divided into a reading sub-state machine and a writing sub-state machine. See the source comments in statem.c for a more detailed description of the various states and transitions possible. Conceptually the state machine component is designed as follows: libssl | ---------------------------|-----statem.h-------------------------------------- | _______V____________________ | | | statem.c | | | | Core state machine code | |____________________________| statem_locl.h ^ ^ _________| |_______ | | _____________|____________ _____________|____________ | | | | | statem_clnt.c | | statem_srvr.c | | | | | | TLS/DTLS client specific | | TLS/DTLS server specific | | state machine code | | state machine code | |__________________________| |__________________________| | |_______________|__ | | ________________| | | | | | | ____________V_______V________ ________V______V_______________ | | | | | statem_both.c | | statem_dtls.c | | | | | | Non core functions common | | Non core functions common to | | to both servers and clients | | both DTLS servers and clients | |_____________________________| |_______________________________|