Lines Matching refs:a
104 | MBEDTLS_SSL_ENCRYPT_THEN_MAC | n/a |
105 | MBEDTLS_SSL_EXTENDED_MASTER_SECRET | n/a |
107 | MBEDTLS_SSL_RENEGOTIATION | n/a |
117 | MBEDTLS_KEY_EXCHANGE_PSK_ENABLED | n/a (2) |
118 | MBEDTLS_KEY_EXCHANGE_DHE_PSK_ENABLED | n/a |
119 | MBEDTLS_KEY_EXCHANGE_ECDHE_PSK_ENABLED | n/a |
120 | MBEDTLS_KEY_EXCHANGE_RSA_PSK_ENABLED | n/a |
121 | MBEDTLS_KEY_EXCHANGE_RSA_ENABLED | n/a |
122 | MBEDTLS_KEY_EXCHANGE_DHE_RSA_ENABLED | n/a |
123 | MBEDTLS_KEY_EXCHANGE_ECDHE_RSA_ENABLED | n/a |
124 | MBEDTLS_KEY_EXCHANGE_ECDHE_ECDSA_ENABLED | n/a |
125 | MBEDTLS_KEY_EXCHANGE_ECDH_ECDSA_ENABLED | n/a |
126 | MBEDTLS_KEY_EXCHANGE_ECDH_RSA_ENABLED | n/a |
127 | MBEDTLS_KEY_EXCHANGE_ECJPAKE_ENABLED | n/a |
165 The following coding rules are aimed to be a checklist for TLS 1.3 upstreaming
183 - The names of macros and variables related to a field or structure in the
196 - Regarding vectors that are represented by a length followed by their value
199 - Use `<vector name>_len` for the name of a variable used to compute the
203 - Use `p_<vector_name>_len` for the name of a variable intended to hold
206 - Use `<vector_name>` for the name of a variable intended to hold the
209 - Use `<vector_name>_end` for the name of a variable intended to hold
224 - the macros to extract a byte from a multi-byte integer MBEDTLS_BYTE_{0-8}.
225 - the macros to write in memory in big-endian order a multi-byte integer
227 - the macros to read from memory a multi-byte integer in big-endian order
241 check that we do not write or read past the end of a data buffer. The
243 to read/write past the end of a data buffer.
254 happening again, use always a local variable named `p` for the reading
259 - When an TLS 1.3 structure is written or read by a function or as part of
260 a function, provide as documentation the definition of the structure as
284 places in the code. When a constant is used only locally in a function
286 writing TLS handshake message) there is no need to define a macro for it.
290 - When declaring a pointer the dereferencing operator should be prepended to
302 - A line can be more than 80 characters by a few characters if just looking
307 If a line becomes too long due to a refactoring (for example renaming a
308 function to a longer name, or indenting a block more), avoid rewrapping
323 - When a function's parameters span several lines, group related parameters
343 The TLS 1.3 handshake protocol is implemented as a state machine. The
345 functions of that implementation. They are implemented as a switch over all the
352 result in too many checks of whether something needs to be done or not in a
355 bypassed if the handshake is based on a pre-shared key and thus does not
361 client side is a example of that.
366 handlers is split into a sequence of stages.
369 between the calls to the handlers and as a consequence handlers do not have to
381 will be, an example of that on client side being if we are going to receive a
388 a coordination stage involving the next record type reading, the next