Skip to main content
  • Home
  • login
  • Browse the archive

    swh mirror partner logo
swh logo
SoftwareHeritage
Software
Heritage
Mirror
Features
  • Search

  • Downloads

  • Save code now

  • Add forge now

  • Help

  • 69ad490
  • /
  • ssl
  • /
  • statem
  • /
  • README.md
Raw File
Permalinks

To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.

  • content
  • directory
content badge Iframe embedding
swh:1:cnt:ee49ed986371c54935e905b02de3d5764bdc2114
directory badge Iframe embedding
swh:1:dir:68b3df26e9fab289c91bdf62bb4b29c32ba7d6ee
README.md
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_lib.c                | | statem_dtls.c                 |
    |                             | |                               |
    | Non core functions common   | | Non core functions common to  |
    | to both servers and clients | | both DTLS servers and clients |
    |_____________________________| |_______________________________|

ENEA — Copyright (C), ENEA. License: GNU AGPLv3+.
Legal notes  ::  JavaScript license information ::  Web API

back to top