openssl/ssl/statem
2020-07-05 11:29:43 +02:00
..
extensions_clnt.c Don't send supported groups if no-ec and we're doing DTLS 2020-06-19 10:19:32 +01:00
extensions_cust.c Reorganize local header files 2019-09-28 20:26:35 +02:00
extensions_srvr.c Modify libssl to discover supported groups based on available providers 2020-06-19 10:19:31 +01:00
extensions.c Do not allow dropping Extended Master Secret extension on renegotiaton 2020-06-09 14:11:19 +02:00
README.md Fix many MarkDown issues in {NOTES*,README*,HACKING,LICENSE}.md files 2020-07-05 11:29:43 +02:00
statem_clnt.c Don't downgrade keys in libssl 2020-06-05 11:04:11 +01:00
statem_dtls.c Reorganize local header files 2019-09-28 20:26:35 +02:00
statem_lib.c SSL_OP_DISABLE_TLSEXT_CA_NAMES option implementation 2020-05-07 16:14:47 +03:00
statem_local.h Update copyright year 2020-06-04 14:33:57 +01:00
statem_srvr.c Fix the DTLS1_COOKIE_LENGTH value 2020-06-19 11:25:35 +01:00
statem.c Reorganize local header files 2019-09-28 20:26:35 +02:00
statem.h Remove function name from errors 2019-07-16 05:26:28 +02:00

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