From c8aaac89d05bf225531793d52d944ab4284da3bb Mon Sep 17 00:00:00 2001 From: Dave Rodgman Date: Mon, 18 Oct 2021 12:56:53 +0100 Subject: [PATCH] Fix naming examples in TLS 1.3 style guide Signed-off-by: Dave Rodgman --- docs/architecture/tls13-experimental.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/architecture/tls13-experimental.md b/docs/architecture/tls13-experimental.md index 5d7c14f1b..88d0b73dd 100644 --- a/docs/architecture/tls13-experimental.md +++ b/docs/architecture/tls13-experimental.md @@ -255,7 +255,7 @@ TLS 1.3 specific coding rules: Example 1: #define CLIENT_HELLO_RANDOM_LEN 32, macro for the length of the `random` field of the ClientHello message. - Example 2 (consistent abbreviation): `mbedtls_ssl_tls1_3_write_sig_alg_ext()` + Example 2 (consistent abbreviation): `mbedtls_ssl_tls13_write_sig_alg_ext()` and `MBEDTLS_TLS_EXT_SIG_ALG`, `sig_alg` standing for `signature_algorithms`. @@ -279,7 +279,7 @@ TLS 1.3 specific coding rules: of another one which could potentially lead to some nasty issues. Example: `cipher_suites` vector of ClientHello in - `ssl_tls1_3_write_client_hello_cipher_suites()` + `ssl_tls13_write_client_hello_cipher_suites()` ``` size_t cipher_suites_len; unsigned char *p_cipher_suites_len;