You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Pavel Barabanov eed703bc81 Fixes crashes in Diablo 3, in AC3, and allows you not to break the launch of guns of fury 11 months ago
..
README.txt Move dead submodules in-tree 11 months ago
config-ccm-psk-tls1_2.h Move dead submodules in-tree 11 months ago
config-mini-tls1_1.h Move dead submodules in-tree 11 months ago
config-no-entropy.h Move dead submodules in-tree 11 months ago
config-suite-b.h Move dead submodules in-tree 11 months ago
config-thread.h Move dead submodules in-tree 11 months ago

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.