Conventions used

There are a number of text conventions used throughout this book.

Code in text indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: ”If the client provides parameters, for example, the set of specific cryptographic algorithms or a key˙share value it wants to use for the TLS handshake, that are not supported by the server, the server replies with a HelloRetryRequest message.”

A block of code is set as follows:

struct {
   uint16 length = Length;
   opaque label <7..255 > = "tls13" + Label;
   opaque context <0..255 > = Context;
} HkdfLabel;

Any command-line input or output is written as follows:

$ gh repo clone duplys/tls_lab
$ cd tls_lab/openssl_docker
$ docker build . -t openssl310