mbedtls/configs
Andrzej Kurek 5902cd64e2 Remove MBEDTLS_SSL_EXPORT_KEYS, making it always on
This option only gated an ability to set a callback,
but was deemed unnecessary as it was yet another define to
remember when writing tests, or test configurations. Fixes #4653.
Signed-off-by: Andrzej Kurek <andrzej.kurek@arm.com>
2021-09-29 10:15:42 -04:00
..
config-ccm-psk-tls1_2.h Make config version symbols optional 2021-06-28 09:28:48 +01:00
config-no-entropy.h Make config version symbols optional 2021-06-28 09:28:48 +01:00
config-suite-b.h Make config version symbols optional 2021-06-28 09:28:48 +01:00
config-symmetric-only.h Make config version symbols optional 2021-06-28 09:28:48 +01:00
config-thread.h Remove MBEDTLS_SSL_EXPORT_KEYS, making it always on 2021-09-29 10:15:42 -04:00
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 mbedtls_config.h. To use one of
them, you can pick one of the following methods:

1. Replace the default file include/mbedtls/mbedtls_config.h with the chosen one.

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.