| /mbedtls/tests/suites/ |
| A D | test_suite_hmac_drbg.function | 188 data_t *custom, data_t *add1,
209 memcpy(data + p_entropy.len, custom->x, custom->len);
211 data, p_entropy.len + custom->len) == 0);
224 custom->x, custom->len) == 0);
238 void hmac_drbg_nopr(int md_alg, data_t *entropy, data_t *custom,
258 custom->x, custom->len) == 0);
274 void hmac_drbg_pr(int md_alg, data_t *entropy, data_t *custom,
293 custom->x, custom->len) == 0);
|
| A D | test_suite_psa_crypto.data | 7563 # Check that with a driver, we reject a custom e as unsupported,
|
| /mbedtls/library/ |
| A D | psa_crypto_random_impl.h | 123 const unsigned char *custom, size_t len) in mbedtls_psa_drbg_seed() argument
126 return mbedtls_ctr_drbg_seed(drbg_ctx, mbedtls_entropy_func, entropy, custom, len); in mbedtls_psa_drbg_seed()
129 return mbedtls_hmac_drbg_seed(drbg_ctx, md_info, mbedtls_entropy_func, entropy, custom, len); in mbedtls_psa_drbg_seed()
|
| A D | hmac_drbg.c | 226 const unsigned char *custom, in mbedtls_hmac_drbg_seed() argument
269 if ((ret = hmac_drbg_reseed_core(ctx, custom, len, in mbedtls_hmac_drbg_seed()
|
| A D | ctr_drbg.c | 538 const unsigned char *custom, in mbedtls_ctr_drbg_seed() argument
583 if ((ret = mbedtls_ctr_drbg_reseed_internal(ctx, custom, len, in mbedtls_ctr_drbg_seed()
|
| /mbedtls/configs/ |
| A D | README.txt | 5 this target. They can be used as a basis for custom configurations.
23 Note that the second method also works if you want to keep your custom
|
| /mbedtls/docs/architecture/ |
| A D | alternative-implementations.md | 12 …s memory management (`calloc`, `free`), `printf`, `exit`. You can define custom functions instead …
22 …is module does not work on your platform, disable `MBEDTLS_NET_C` and use custom functions for TLS.
34 …custom implementation. This is possible for low-level cryptography modules (symmetric algorithms, …
87 For example, to provide a custom `printf` function at run time, enable `MBEDTLS_PLATFORM_PRINTF_ALT…
|
| /mbedtls/include/mbedtls/ |
| A D | hmac_drbg.h | 190 const unsigned char *custom,
|
| A D | ctr_drbg.h | 335 const unsigned char *custom,
|
| /mbedtls/docs/architecture/psa-migration/ |
| A D | psa-limitations.md | 53 extension, servers can still send custom parameters if they don't support the
63 1. Implement support for custom FFDH parameters in PSA Crypto: this would pose
65 the crypto community is moving away from custom FFDH parameters. (Could be
|
| A D | strategy.md | 475 (based on IANA values or custom enums), as is currently done in the new
|
| A D | md-cipher-dispatch.md | 195 * For ciphers, the keystore is not initialized yet, and Mbed TLS uses a custom implementation of PS…
|
| /mbedtls/docs/ |
| A D | psa-driver-example-and-guide.md | 137 …custom configuration that is significantly different to the default. Define the macro for the driv…
|
| A D | 3.0-migration-guide.md | 50 Also, if you have a custom configuration file:
215 If you were using custom config file with `MBEDTLS_SHA256_C` enabled, then
900 to configure a custom session cache implementation different
|
| A D | psa-transition.md | 1072 There is no PSA equivalent to Mbed TLS's custom key type names exposed by `mbedtls_pk_get_name`.
|
| /mbedtls/docs/proposed/ |
| A D | psa-driver-interface.md | 49 …ptographic mechanisms they support. If the driver description references custom types, macros or c…
881 …#c.psa_export_public_key) in the PSA Cryptography API specification. For custom key types defined …
1404 #### Support for custom import formats
1406 …that accepts a custom format would not work with a driver that doesn't accept this format. On the …
1408 …custom formats also causes a problem with import: the core can't know the size of the key represen…
|
| /mbedtls/scripts/data_files/driver_templates/ |
| A D | psa_crypto_driver_wrappers.h.jinja | 746 /* We don't support passing custom production parameters
781 /* We don't support passing custom production parameters
|
| /mbedtls/ |
| A D | ChangeLog | 109 key pair with a custom public exponent.
546 * Fix undefined symbols in some builds using TLS 1.3 with a custom
1143 and possibly up to 571 bytes with a custom cookie check function.
1265 Replace custom LIB_INSTALL_DIR variable with standard CMAKE_INSTALL_LIBDIR
1637 If needed, SHA-1 certificates can still be verified by using a custom
2602 * Remove the technical possibility to define custom mbedtls_md_info
4365 with custom implementation (eg hardware accelerated), complementing the
4467 * Removed mbedtls_timing_msleep(). Use mbedtls_net_usleep() or a custom
4506 custom config.h
5382 * Added support for custom labels when using rsa_rsaes_oaep_encrypt()
[all …]
|