/mbedtls-latest/tests/suites/ |
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);
|
D | test_suite_psa_crypto.data | 6938 PSA key derivation custom: default -> AES-128 6942 PSA key derivation custom: flags=1 -> AES-128 6946 PSA key derivation custom: data non-empty -> AES-128 7535 PSA generate key custom: RSA, flags=1 7539 PSA generate key custom: RSA, empty e 7543 PSA generate key custom: RSA, e=3 7547 PSA generate key custom: RSA, e=3 with leading zeros 7555 #PSA generate key custom: RSA, e=3 with many leading zeros 7559 PSA generate key custom: RSA, e=513 7563 PSA generate key custom: RSA, e=65537 [all …]
|
D | test_suite_psa_crypto.function | 9590 psa_custom_key_parameters_t custom = PSA_CUSTOM_KEY_PARAMETERS_INIT; 9591 custom.flags = flags_arg; 9624 &custom, custom_data->x, custom_data->len, 10222 psa_custom_key_parameters_t custom = PSA_CUSTOM_KEY_PARAMETERS_INIT; 10223 custom.flags = flags_arg; 10236 &custom, custom_data->x, custom_data->len,
|
/mbedtls-latest/library/ |
D | psa_crypto_random_impl.h | 114 const unsigned char *custom, size_t len) in mbedtls_psa_drbg_seed() argument 117 return mbedtls_ctr_drbg_seed(drbg_ctx, mbedtls_entropy_func, entropy, custom, len); in mbedtls_psa_drbg_seed() 120 return mbedtls_hmac_drbg_seed(drbg_ctx, md_info, mbedtls_entropy_func, entropy, custom, len); in mbedtls_psa_drbg_seed()
|
D | psa_crypto_core.h | 404 const psa_custom_key_parameters_t *custom, 431 const psa_custom_key_parameters_t *custom,
|
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()
|
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()
|
D | psa_crypto.c | 6472 const psa_custom_key_parameters_t *custom, argument 6475 if (custom->flags != 0) { 6487 const psa_custom_key_parameters_t *custom, argument 6505 if (!psa_custom_key_parameters_are_default(custom, custom_data_length)) { 7936 const psa_custom_key_parameters_t *custom, argument 7945 (void) custom; 7998 const psa_custom_key_parameters_t *custom, argument 8023 if (custom->flags != 0) { 8028 if (!psa_custom_key_parameters_are_default(custom, custom_data_length)) { 8069 custom,
|
D | psa_crypto_driver_wrappers.h | 841 const psa_custom_key_parameters_t *custom, in psa_driver_wrapper_generate_key() argument 851 psa_custom_key_parameters_are_default(custom, custom_data_length); in psa_driver_wrapper_generate_key() 931 attributes, custom, custom_data, custom_data_length, in psa_driver_wrapper_generate_key()
|
/mbedtls-latest/configs/ |
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-latest/docs/architecture/ |
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-latest/include/mbedtls/ |
D | hmac_drbg.h | 190 const unsigned char *custom,
|
D | ctr_drbg.h | 350 const unsigned char *custom,
|
/mbedtls-latest/include/psa/ |
D | crypto.h | 3840 const psa_custom_key_parameters_t *custom, 4268 const psa_custom_key_parameters_t *custom,
|
/mbedtls-latest/docs/architecture/psa-migration/ |
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
|
D | strategy.md | 475 (based on IANA values or custom enums), as is currently done in the new
|
D | md-cipher-dispatch.md | 195 * For ciphers, the keystore is not initialized yet, and Mbed TLS uses a custom implementation of PS…
|
/mbedtls-latest/docs/ |
D | psa-driver-example-and-guide.md | 137 …custom configuration that is significantly different to the default. Define the macro for the driv…
|
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
|
D | driver-only-builds.md | 281 Mbed TLS legacy API supports custom groups. As a consequence, the TLS layer
|
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-latest/scripts/data_files/driver_templates/ |
D | psa_crypto_driver_wrappers.h.jinja | 734 const psa_custom_key_parameters_t *custom, 744 psa_custom_key_parameters_are_default(custom, custom_data_length); 747 /* We don't support passing custom production parameters 782 /* We don't support passing custom production parameters 815 attributes, custom, custom_data, custom_data_length,
|
/mbedtls-latest/docs/proposed/ |
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-latest/ |
D | ChangeLog | 49 - Finite-field Diffie-Hellman with custom groups. 192 When migrating from Mbed TLS 2.x, if you had a custom config.h that 303 key pair with a custom public exponent. 741 * Fix undefined symbols in some builds using TLS 1.3 with a custom 1338 and possibly up to 571 bytes with a custom cookie check function. 1460 Replace custom LIB_INSTALL_DIR variable with standard CMAKE_INSTALL_LIBDIR 1832 If needed, SHA-1 certificates can still be verified by using a custom 2797 * Remove the technical possibility to define custom mbedtls_md_info 4560 with custom implementation (eg hardware accelerated), complementing the 4662 * Removed mbedtls_timing_msleep(). Use mbedtls_net_usleep() or a custom [all …]
|