Lines Matching +full:- +full:a
6 * This set of compile-time options may be used to enable
11 * Copyright (C) 2006-2018, ARM Limited, All Rights Reserved
12 * SPDX-License-Identifier: Apache-2.0
16 * You may obtain a copy of the License at
18 * http://www.apache.org/licenses/LICENSE-2.0
66 * The platform lacks support for double-width integer division (64-bit
67 * division on a 32-bit platform, 128-bit division on a 64-bit platform).
73 * The bignum code uses double-width division to speed up some operations.
74 * Double-width division is often implemented in software that needs to
75 * be linked with the program. The presence of a double-width integer
80 * Uncomment this option to prevent the use of double-width division.
83 * Furthermore, a 64-bit type is always required even on a 32-bit
85 * cases it is also desirable to disable some double-width operations. For
86 * example, if double-width division is implemented in software, disabling
94 * The platform lacks support for 32x32 -> 64-bit multiplication.
99 * Some parts of the library may use multiplication of two unsigned 32-bit
100 * operands with a 64-bit result in order to speed up computations. On some
102 * software, usually in a library provided by the toolchain.
105 * removes the dependency of that library on platforms that lack a hardware
106 * 64-bit multiplier by embedding a software implementation in Mbed TLS.
118 * Uncomment if the CPU supports SSE2 (IA-32 specific).
146 * Comment if your system does not have a correct clock.
153 * mbedtls_platform_gmtime_r() at compile-time by using the macro
163 * By default mbed TLS uses the system-provided calloc() and free().
164 * This allows different allocators (self-implemented or provided) to be
191 * the MBEDTLS_PLATFORM_STD_XXX defines, or enabling a
204 * MBEDTLS_PLATFORM_XXX_ALT: Uncomment a macro to let mbed TLS support the
208 * provide a function "mbedtls_platform_set_printf()" that allows you to set an
221 * Uncomment a macro to enable alternate implementation of specific base
236 * Mark deprecated functions so that they generate a warning if used.
238 * version. You can enable this to help you prepare the transition to a new
253 * version. You can enable this to help you prepare the transition to a new
269 * internal memory errors such as overflowing a buffer controlled by the
277 * For example, when a function accepts as input a pointer to a buffer that may
280 * - The pointer is checked to be non-NULL only if this option is enabled.
281 * - The content of the buffer is always validated.
283 * When this flag is defined, if a library function receives a parameter that
290 * When defining this flag, you also need to arrange a definition for
292 * - By default, the library defines MBEDTLS_PARAM_FAILED() to call a
297 * - If you enable the macro #MBEDTLS_CHECK_PARAMS_ASSERT, then the
301 * - If you define a macro MBEDTLS_PARAM_FAILED() before including `config.h`
308 * Uncomment to enable validation of application-controlled parameters.
319 * calling a function mbedtls_param_failed(). See the documentation of
344 * You will need to provide a header "timing_alt.h" and an implementation at
352 * MBEDTLS__MODULE_NAME__ALT: Uncomment a macro to let mbed TLS use your
353 * alternate core implementation of a symmetric crypto, an arithmetic or hash
365 * Uncomment a macro to enable alternate implementation of the corresponding
368 * \warning MD2, MD4, MD5, ARC4, DES and SHA-1 are considered weak and their
369 * use constitutes a security risk. If possible, we recommend
402 * - ecp.c
403 * - ecp_curves.c
413 * MBEDTLS__FUNCTION_NAME__ALT: Uncomment a macro to let mbed TLS use you
426 * \note Because of a signature change, the core AES encryption and decryption routines are
433 * MBEDTLS_AES_ROM_TABLES in order to help the linker garbage-collect the AES
436 * Uncomment a macro to enable alternate implementation of the corresponding
439 * \warning MD2, MD4, MD5, DES and SHA-1 are considered weak and their use
440 * constitutes a security risk. If possible, we recommend avoiding
468 * Expose a part of the internal interface of the Elliptic Curve Point module.
470 * MBEDTLS_ECP__FUNCTION_NAME__ALT: Uncomment a macro to let mbed TLS use your
502 * Uncomment a macro to enable alternate implementation of the corresponding
538 * Uncomment this macro to let mbed TLS use your own implementation of a
576 * (the tables are entry-wise rotations of one another).
630 * Enable Xor-encrypt-xor with ciphertext stealing mode (XTS) for AES.
696 * \warning DES is considered a weak cipher and its use constitutes a
723 * A man-in-the-browser attacker can recover authentication tokens sent through
724 * a TLS connection using a 3DES based cipher suite (see "On the Practical
725 * (In-)Security of 64-bit Block Ciphers" by Karthikeyan Bhargavan and Gaëtan
770 * Enable "non-blocking" ECC operations that can return early and be resumed.
777 * number of ECC operations a function may perform before pausing; see
780 * This is useful in non-threaded environments if you want to avoid blocking
795 * Use a backward compatible ECDH context.
803 * (56 bytes on a 32-bit platform). In future versions of the library, it
825 * may result in a compromise of the long-term signing key. This is avoided by
859 * Enable the DHE-PSK based ciphersuite modes in SSL / TLS.
878 * \warning Using DHE constitutes a security risk as it
890 * Enable the ECDHE-PSK based ciphersuite modes in SSL / TLS.
910 * Enable the RSA-PSK based ciphersuite modes in SSL / TLS.
935 * Enable the RSA-only based ciphersuite modes in SSL / TLS.
963 * Enable the DHE-RSA based ciphersuite modes in SSL / TLS.
984 * \warning Using DHE constitutes a security risk as it
996 * Enable the ECDHE-RSA based ciphersuite modes in SSL / TLS.
1021 * Enable the ECDHE-ECDSA based ciphersuite modes in SSL / TLS.
1045 * Enable the ECDH-ECDSA based ciphersuite modes in SSL / TLS.
1069 * Enable the ECDH-RSA based ciphersuite modes in SSL / TLS.
1095 * \warning This is currently experimental. EC J-PAKE support is based on the
1126 * Enable a dummy error function to make use of mbedtls_strerror() in
1141 * Enable the prime-number generation code.
1170 * Do not use built-in platform entropy functions.
1174 * Uncomment this macro to disable the built-in platform entropy functions.
1181 * Force the entropy accumulator to use a SHA-256 accumulator instead of the
1182 * default SHA-512 based one (if both are available).
1186 * On 32-bit systems SHA-256 can be much faster than SHA-512. Use this option
1197 * Enable the non-volatile (NV) seed file-based entropy source.
1200 * This is crucial (if not required) on systems that do not have a
1207 * compile-time depending on the flags (MBEDTLS_PLATFORM_NV_SEED_*) used.
1209 * \note If you use the default implementation functions that read a seedfile
1210 * with regular fopen(), please make sure you make a seedfile with the
1241 * GLIBC-compatible backtrace() an backtrace_symbols() support
1250 * Support external private RSA keys (eg from a HSM) in the PK layer.
1274 * This enables support for RSAES-OAEP and RSASSA-PSS operations.
1282 * Partition Manager) integration which separates the code into two parts: a
1283 * NSPE (Non-Secure Process Environment) and an SPE (Secure Process
1296 * required on systems that do not have a built-in entropy source (TRNG).
1297 * This feature is currently not supported on systems that have a built-in
1326 * Enable an implementation of SHA-256 that has lower ROM footprint but also
1329 * The default implementation is meant to be a reasonnable compromise between
1331 * the expense of performance. Eg on Cortex-M4 it reduces the size of
1332 * mbedtls_sha256_process() from ~2KB to ~0.5KB for a performance hit of about
1371 * (version draft-ietf-tls-dtls-connection-id-05,
1372 * https://tools.ietf.org/html/draft-ietf-tls-dtls-connection-id-05)
1386 * - MBEDTLS_SSL_CID_OUT_LEN_MAX
1387 * - MBEDTLS_SSL_CID_IN_LEN_MAX.
1412 * This pair of functions allows one side of a connection to serialize the
1413 * context associated with the connection, then free or re-use that context
1415 * that state to a live context for resuming read/write operations on the
1416 * connection. From a protocol perspective, the state of the connection is
1421 * establishing new connections associated to a saved session with shorter,
1422 * lighter handshakes, while context serialization is a local optimization in
1423 * handling a single, potentially long-lived connection.
1444 * a timing side-channel.
1451 * Enable support for Encrypt-then-MAC, RFC 7366.
1453 * This allows peers that both support it to use a more robust protection for
1463 * Comment this macro to disable support for Encrypt-then-MAC
1470 * (draft-ietf-tls-session-hash-02).
1474 * renegotiation), since it actually fixes a more fundamental issue in the
1488 * Enable support for FALLBACK_SCSV (draft-ietf-tls-downgrade-scsv-00).
1492 * implements a fallback strategy.
1494 * For clients, you only need this if you're using a fallback strategy, which
1496 * interoperate with buggy (version-intolerant) servers.
1517 * for exaple by keeping a hash of the peer's certificate.
1537 * Enable 1/n-1 record splitting for CBC mode in SSLv3 and TLS 1.0.
1539 * This is a countermeasure to the BEAST attack, which also minimizes the risk
1540 * of interoperability issues compared to sending 0-length records.
1542 * Comment this macro to disable 1/n-1 record splitting.
1551 * The two main uses of renegotiation are (1) refresh keys on long-lived
1672 * Enable support for the anti-replay mechanism in DTLS.
1677 * \warning Disabling this is often a security risk!
1680 * Comment this to disable anti-replay in DTLS.
1691 * unless you know for sure amplification cannot be a problem in the
1694 * \warning Disabling this can ba a security risk! (see above)
1705 * Enable server-side support for clients that reconnect from the same port.
1721 * Enable support for a limit of records with bad MAC.
1733 * Client-side, provides full support for session tickets (maintenance of a
1735 * Server-side, you also need to provide callbacks for writing and parsing
1747 * This is required for certain users of TLS, e.g. EAP-TLS.
1776 * Fallback to old (pre-2.7), non-conforming implementation of the truncated
1778 * only meant for a transitory upgrade period and is likely to be removed in
1779 * a future version of the library.
1781 * \warning The old implementation is non-compliant and has a security weakness
1782 * (2^80 brute force attack on the HMAC key used for a single,
1786 * the fixed implementation yet (pre-2.7).
1788 * \deprecated This option is deprecated and will likely be removed in a
1791 * Uncomment to fallback to old, non-compliant truncated HMAC implementation.
1837 * now, access to these APIs is opt-in (via enabling the present option), in
1849 * Allow run-time checking of compile-time enabled features. Thus allowing users
1850 * to check at run-time if the library is for instance compiled with threading
1855 * Comment this to disable run-time checking and save ROM space
1862 * If set, the X509 parser will not break-off when parsing an X509 certificate
1863 * and encountering an extension in a v1 or v2 certificate.
1872 * If set, the X509 parser will not break-off when parsing an X509 certificate
1875 * \warning Depending on your PKI use, enabling this can be a security risk!
1886 * the set of trusted certificates through a callback instead of a linked
1889 * This is useful for example in environments where a large number of trusted
1890 * certificates is present and storing them in a linked list isn't efficient
1905 * Disabling this avoids problems with mis-issued and/or misused
1908 * \warning Depending on your PKI use, disabling this can be a security risk!
1919 * Disabling this avoids problems with mis-issued and/or misused certificates.
1921 * \warning Depending on your PKI use, disabling this can be a security risk!
1931 * signed with RSASSA-PSS (aka PKCS#1 v2.1).
1933 * Comment this macro to disallow using RSASSA-PSS in certificates.
1943 * \warning TLS-level compression MAY REDUCE SECURITY! See for example the
1973 * Enable AES-NI support on x86-64.
1980 * This modules adds support for the AES-NI instructions on x86-64
2080 * \warning ARC4 is considered a weak cipher and its use constitutes a
2130 * Enable the multi-precision integer library.
2263 * Enable the Counter with CBC-MAC (CCM) mode for 128-bit block cipher.
2269 * This module enables the AES-CCM ciphersuites, if other requisites are
2298 * Enable the ChaCha20-Poly1305 AEAD algorithm.
2321 * Enable the CMAC (Cipher-based Message Authentication Code) mode for block
2334 * Enable the CTR_DRBG AES-based random generator.
2335 * The CTR_DRBG generator uses AES-256 by default.
2336 * To use AES-128 instead, enable MBEDTLS_CTR_DRBG_USE_128_BIT_KEY below.
2385 * \warning DES is considered a weak cipher and its use constitutes a
2393 * Enable the Diffie-Hellman-Merkle module.
2400 * DHE-RSA, DHE-PSK
2402 * \warning Using DHE constitutes a security risk as it
2414 * Enable the elliptic curve Diffie-Hellman library.
2421 * ECDHE-ECDSA, ECDHE-RSA, DHE-PSK
2436 * ECDHE-ECDSA
2445 * Enable the elliptic curve J-PAKE library.
2447 * \warning This is currently experimental. EC J-PAKE support is based on the
2478 * Enable the platform-specific entropy code.
2485 * This module provides a generic entropy pool
2510 * This module enables the AES-GCM and CAMELLIA-GCM ciphersuites, if other
2526 * input. As a secondary input to your entropy pool, it IS able add
2549 * (HMAC)-based key derivation function (HKDF).
2570 * Enable the Key Wrapping mode for 128-bit block ciphers,
2571 * as defined in NIST SP 800-38F. Only KW and KWP modes
2600 * Uncomment to enable support for (rare) MD2-signed X.509 certs.
2602 * \warning MD2 is considered a weak message digest and its use constitutes a
2617 * Uncomment to enable support for (rare) MD4-signed X.509 certs.
2619 * \warning MD4 is considered a weak message digest and its use constitutes a
2638 * MD5-signed certificates, and for PBKDF1 when decrypting PEM-encoded
2641 * \warning MD5 is considered a weak message digest and its use constitutes a
2651 * Enable the buffer allocator implementation that makes use of a (stack)
2673 * \note See also our Knowledge Base article about porting to a new
2675 * https://tls.mbed.org/kb/how-to/how-do-i-port-mbed-tls-to-a-new-environment-OS
2823 * Requires the presence of the PKCS#11 helper library (libpkcs11-helper)
2846 * Enable the platform abstraction layer that allows you to re-assign
2854 * as other module rely on it for a fixed snprintf implementation.
2897 * either MBEDTLS_PSA_ITS_FILE_C or a native implementation of
2918 * Enable the RIPEMD-160 hash algorithm.
2929 * Enable the RSA public-key cryptosystem.
2939 * RSA, DHE-RSA, ECDHE-RSA, RSA-PSK
2958 * depending on the handshake parameters, and for SHA1-signed certificates.
2960 * \warning SHA-1 is considered a weak message digest and its use constitutes
2961 * a security risk. If possible, we recommend avoiding dependencies
2970 * Enable the SHA-224 and SHA-256 cryptographic hash algorithms.
2979 * This module adds support for SHA-224 and SHA-256.
2987 * Enable the SHA-384 and SHA-512 cryptographic hash algorithms.
2995 * This module adds support for SHA-384 and SHA-512.
3024 * Enable an implementation of TLS server-side callbacks for session tickets.
3081 * By default mbed TLS assumes it is used in a non-threaded environment or that
3085 * https://tls.mbed.org/kb/development/thread-safety-and-multi-threading
3089 * This allows different threading implementations (self-implemented or
3102 * Enable the semi-portable timing interface.
3111 * \note See also our Knowledge Base article about porting to a new
3113 * https://tls.mbed.org/kb/how-to/how-do-i-port-mbed-tls-to-a-new-environment-OS
3125 * Enable run-time version information.
3129 * This module provides run-time version information.
3253 * only if you have a good reason and know the consequences.
3265 … 48 /**< Amount of entropy used per seed by default (48 with SHA-512, 32 with SHA-256) */
3270 //#define MBEDTLS_CTR_DRBG_USE_128_BIT_KEY /**< Use 128-bit key for CTR_DRBG - may red…
3281 //#define MBEDTLS_ECP_FIXED_POINT_OPTIM 1 /**< Enable fixed-point speed-up */
3299 /* Note: your snprintf must correctly zero-terminate the buffer! */
3316 /* Note: your snprintf must correctly zero-terminate the buffer! */
3328 * a default definition. If the macro #MBEDTLS_CHECK_PARAMS_ASSERT
3330 * otherwise the default definition calls a function
3340 * from within the library - you can ensure that by providing
3349 * parameters only in non-void functions, and void function will
3369 * in such a way that both are capable of holding the specified amount of
3376 * \note When using a value less than the default of 16KB on the client, it is
3394 * This determines the size of the incoming TLS I/O buffer in such a way
3401 * \note When using a value less than the default of 16KB on the client, it is
3435 * padded plaintext is a multiple of the value of this option.
3437 * Note: A value of \c 1 means that no padding will be used
3441 * a power of two should be preferred.
3450 * This determines the size of the outgoing TLS I/O buffer in such a way
3457 * It is possible to save RAM by setting a smaller outward buffer, while keeping
3472 * Maximum number of heap-allocated bytes for the purpose of
3476 * to account for a reassembled handshake message of maximum size,
3479 * A value of 2 * MBEDTLS_SSL_IN_CONTENT_LEN (32768 by default)
3481 * to reassembly a large handshake message (such as a certificate)
3488 //#define MBEDTLS_PSK_MAX_LEN 32 /**< Max size of TLS pre-shared keys, in bytes (defa…
3498 * Use this to save a few hundred bytes of ROM (default ordering of all
3499 * available ciphersuites) and a few to a few hundred bytes of RAM.
3506 //#define MBEDTLS_X509_MAX_INTERMEDIATE_CA 8 /**< Maximum number of intermediate CAs in a verif…
3507 //#define MBEDTLS_X509_MAX_FILE_PATH_LEN 512 /**< Maximum length of a path/filename string in b…
3510 * Allow SHA-1 in the default TLS configuration for certificate signing.
3511 * Without this build-time option, SHA-1 support must be activated explicitly
3513 * recommended because of it is possible to generate SHA-1 collisions, however
3516 * \warning SHA-1 is considered a weak message digest and its use constitutes
3517 * a security risk. If possible, we recommend avoiding dependencies
3524 * Allow SHA-1 in the default TLS configuration for TLS 1.2 handshake
3525 * signature and ciphersuite selection. Without this build-time option, SHA-1
3527 * The use of SHA-1 in TLS <= 1.1 and in HMAC-SHA-1 is always allowed by
3529 * of SHA-1 in handshake signatures, hence this option is turned on by default
3533 * \warning SHA-1 is considered a weak message digest and its use constitutes
3534 * a security risk. If possible, we recommend avoiding dependencies
3545 * mbedtls_platform_zeroize() is a widely used function across the library to
3546 * zero a block of memory. The implementation is expected to be secure in the
3551 * versions of the C language standards do not provide a secure implementation
3555 * C standards (e.g using memset_s() in C11) or calling a secure memset() from
3565 * gmtime() is not a thread-safe function as defined in the C standard. The
3582 * contexts and therefore is a compatibility break for applications that access
3583 * fields of a mbedtls_ecdh_context structure directly. See also