Todd Short 10ed1b7239 Reorder extensions to put SigAlgs last 7 years ago
..
README f0de395950 Add a state machine README 9 years ago
extensions.c 10ed1b7239 Reorder extensions to put SigAlgs last 7 years ago
extensions_clnt.c 10ed1b7239 Reorder extensions to put SigAlgs last 7 years ago
extensions_cust.c 67dc995eaf Move ossl_assert 7 years ago
extensions_srvr.c 44e6995155 Fix some Typos and indents 7 years ago
statem.c 75e2c87765 Switch from ossl_rand to DRBG rand 7 years ago
statem.h bd79bcb42b Remove special case code for SCTP reneg handling 7 years ago
statem_clnt.c ae3947de09 Add a DRBG to each SSL object 7 years ago
statem_dtls.c 67dc995eaf Move ossl_assert 7 years ago
statem_lib.c 67dc995eaf Move ossl_assert 7 years ago
statem_locl.h 3a7c56b2c0 Add TLSv1.3 server side external PSK support 7 years ago
statem_srvr.c 5626f634c3 Move ALPN handling from finalizer to delayed call 7 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_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 |
|_____________________________| |_______________________________|