• Home
  • Annotate
  • current directory
Name Date Size #Lines LOC

..22-Aug-2025-

ext/21-Aug-2025-

README.txt A D21-Aug-2025953 2516

config-ccm-psk-dtls1_2.h A D21-Aug-20252.1 KiB6720

config-ccm-psk-tls1_2.h A D21-Aug-20251.8 KiB5912

config-suite-b.h A D21-Aug-20251.6 KiB5413

config-symmetric-only.h A D21-Aug-2025366 174

config-tfm.h A D21-Aug-2025329 131

config-thread.h A D21-Aug-20251.1 KiB4413

crypto-config-ccm-psk-tls1_2.h A D21-Aug-20251 KiB4013

crypto-config-suite-b.h A D21-Aug-20252.1 KiB7433

crypto-config-thread.h A D21-Aug-20252.1 KiB7134

README.txt

1This directory contains example configuration files.
2
3The examples are generally focused on a particular usage case (eg, support for
4a restricted number of ciphersuites) and aim at minimizing resource usage for
5this target. They can be used as a basis for custom configurations.
6
7These files are complete replacements for the default mbedtls_config.h. To use one of
8them, you can pick one of the following methods:
9
101. Replace the default file include/mbedtls/mbedtls_config.h with the chosen one.
11
122. Define MBEDTLS_CONFIG_FILE and adjust the include path accordingly.
13   For example, using make:
14
15    CFLAGS="-I$PWD/configs -DMBEDTLS_CONFIG_FILE='<foo.h>'" make
16
17   Or, using cmake:
18
19    find . -iname '*cmake*' -not -name CMakeLists.txt -exec rm -rf {} +
20    CFLAGS="-I$PWD/configs -DMBEDTLS_CONFIG_FILE='<foo.h>'" cmake .
21    make
22
23Note that the second method also works if you want to keep your custom
24configuration file outside the Mbed TLS tree.
25