mirror of
https://github.com/yuzu-emu/mbedtls.git
synced 2024-11-27 05:24:15 +01:00
e965bd397e
This commit introduces the numeric compile-time constants - MBEDTLS_SSL_CONF_MIN_MINOR_VER - MBEDTLS_SSL_CONF_MAX_MINOR_VER - MBEDTLS_SSL_CONF_MIN_MAJOR_VER - MBEDTLS_SSL_CONF_MAX_MAJOR_VER which, when defined, overwrite the runtime configurable fields mbedtls_ssl_config::min_major_ver etc. in the SSL configuration. As for the preceding case of the ExtendedMasterSecret configuration, it also introduces and puts to use getter functions for these variables which evaluate to either a field access or the macro value, maintaining readability of the code. The runtime configuration API mbedtls_ssl_conf_{min|max}_version() is kept for now but has no effect if MBEDTLS_SSL_CONF_XXX are set. This is likely to be changed in a later commit but deliberately omitted for now, in order to be able to study code-size benefits earlier in the process. |
||
---|---|---|
.. | ||
baremetal_test.h | ||
baremetal.h | ||
config-ccm-psk-tls1_2.h | ||
config-mini-tls1_1.h | ||
config-no-entropy.h | ||
config-suite-b.h | ||
config-thread.h | ||
README.txt |
This directory contains example configuration files. The examples are generally focused on a particular usage case (eg, support for a restricted number of ciphersuites) and aim at minimizing resource usage for this target. They can be used as a basis for custom configurations. These files are complete replacements for the default config.h. To use one of them, you can pick one of the following methods: 1. Replace the default file include/mbedtls/config.h with the chosen one. (Depending on your compiler, you may need to adjust the line with #include "mbedtls/check_config.h" then.) 2. Define MBEDTLS_CONFIG_FILE and adjust the include path accordingly. For example, using make: CFLAGS="-I$PWD/configs -DMBEDTLS_CONFIG_FILE='<foo.h>'" make Or, using cmake: find . -iname '*cmake*' -not -name CMakeLists.txt -exec rm -rf {} + CFLAGS="-I$PWD/configs -DMBEDTLS_CONFIG_FILE='<foo.h>'" cmake . make Note that the second method also works if you want to keep your custom configuration file outside the mbed TLS tree.