Searched refs:custom (Results 1 – 13 of 13) sorted by relevance
/mbedtls-development/tests/suites/ |
A D | test_suite_hmac_drbg.function | 179 data_t * custom, data_t * add1, 198 memcpy( data + p_entropy.len, custom->x, custom->len ); 200 data, p_entropy.len + custom->len ) == 0 ); 213 custom->x, custom->len ) == 0 ); 226 void hmac_drbg_nopr( int md_alg, data_t * entropy, data_t * custom, 244 custom->x, custom->len ) == 0 ); 259 void hmac_drbg_pr( int md_alg, data_t * entropy, data_t * custom, 276 custom->x, custom->len ) == 0 );
|
A D | test_suite_ssl.function | 111 * Buffer structure for custom I/O callbacks.
|
/mbedtls-development/library/ |
A D | psa_crypto_random_impl.h | 185 const unsigned char *custom, size_t len ) in mbedtls_psa_drbg_seed() argument 191 custom, len ) ); in mbedtls_psa_drbg_seed() 199 custom, len ) ); in mbedtls_psa_drbg_seed()
|
A D | hmac_drbg.c | 239 const unsigned char *custom, in mbedtls_hmac_drbg_seed() argument 281 if( ( ret = hmac_drbg_reseed_core( ctx, custom, len, in mbedtls_hmac_drbg_seed()
|
A D | ctr_drbg.c | 437 const unsigned char *custom, in mbedtls_ctr_drbg_seed() argument 474 if( ( ret = mbedtls_ctr_drbg_reseed_internal( ctx, custom, len, in mbedtls_ctr_drbg_seed()
|
/mbedtls-development/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-development/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-development/include/mbedtls/ |
A D | hmac_drbg.h | 203 const unsigned char *custom,
|
A D | ctr_drbg.h | 332 const unsigned char *custom,
|
/mbedtls-development/docs/proposed/ |
A D | psa-driver-interface.md | 47 …ptographic mechanisms they support. If the driver description references custom types, macros or c… 444 …#c.psa_export_public_key) in the PSA Cryptography API specification. For custom key types defined … 961 #### Support for custom import formats 963 …that accepts a custom format would not work with a driver that doesn't accept this format. On the … 965 …custom formats also causes a problem with import: the core can't know the size of the key represen…
|
/mbedtls-development/doxygen/ |
A D | mbedtls.doxyfile | 253 # that for custom extensions you also need to set FILE_PATTERNS otherwise the 896 # standard header. Note that when using a custom header you are responsible 1095 # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to 1097 # http://doc.trolltech.com/qthelpproject.html#custom-filters 1102 # custom filter to add. For more information please see 1103 # <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
|
/mbedtls-development/docs/ |
A D | 3.0-migration-guide.md | 29 Also, if you have a custom configuration file: 194 If you were using custom config file with `MBEDTLS_SHA256_C` enabled, then 872 to configure a custom session cache implementation different
|
/mbedtls-development/ |
A D | ChangeLog | 187 If needed, SHA-1 certificates can still be verified by using a custom 1151 * Remove the technical possibility to define custom mbedtls_md_info 2914 with custom implementation (eg hardware accelerated), complementing the 3016 * Removed mbedtls_timing_msleep(). Use mbedtls_net_usleep() or a custom 3055 custom config.h 3931 * Added support for custom labels when using rsa_rsaes_oaep_encrypt() 4174 custom entropy sources and added some generic and platform dependent
|
Completed in 28 milliseconds