Matt Caswell 09b3654096 Make sure we always send an alert in libssl if we hit a fatal error 4 years ago
..
README 706457b7bd Reorganize local header files 5 years ago
extensions.c fc69f32cd6 Use EVP_DigestSignInit_ex and EVP_DigestVerifyInit_ex in libssl 4 years ago
extensions_clnt.c afce590b74 TLS: Temporarly downgrade newly generated EVP_PKEYs to legacy 4 years ago
extensions_cust.c 706457b7bd Reorganize local header files 5 years ago
extensions_srvr.c afce590b74 TLS: Temporarly downgrade newly generated EVP_PKEYs to legacy 4 years ago
statem.c 706457b7bd Reorganize local header files 5 years ago
statem.h aac96e2797 Remove function name from errors 5 years ago
statem_clnt.c afce590b74 TLS: Temporarly downgrade newly generated EVP_PKEYs to legacy 4 years ago
statem_dtls.c 706457b7bd Reorganize local header files 5 years ago
statem_lib.c a959b4fa97 Use X509_STORE_CTX_new_with_libctx() in libssl 4 years ago
statem_local.h 706457b7bd Reorganize local header files 5 years ago
statem_srvr.c 09b3654096 Make sure we always send an alert in libssl if we hit a fatal error 4 years ago

README

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_local.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 |
|_____________________________| |_______________________________|