| /mbedtls-latest/tests/suites/ |
| D | test_suite_block_cipher.function | 35 /* Bad parameters to setup */
41 /* setkey() before successful setup() */
45 /* encrypt() before successful setup() */
49 /* free() before successful setup()
53 /* Now properly setup the context */
|
| D | test_suite_psa_crypto_driver_wrappers.data | 637 Hash multi-part setup: SHA-256, computed by the driver
641 Hash multi-part setup: SHA-256, fallback
645 Hash multi-part setup: SHA-256, no fallback
649 Hash multi-part setup: SHA-256, INSUFFICIENT_MEMORY
804 PSA AEAD encrypt setup, AES-GCM, 128 bytes #1
808 PSA AEAD encrypt setup, AES-GCM, 128 bytes #1, fallback
812 PSA AEAD encrypt setup, AES-GCM, 128 bytes #1, INSUFFICIENT_MEMORY
816 PSA AEAD decrypt setup, AES-GCM, 144 bytes #1
820 PSA AEAD decrypt setup, AES-GCM, 144 bytes #1, fallback
824 PSA AEAD decrypt setup, AES-GCM, 144 bytes #1, insufficient memory
[all …]
|
| D | test_suite_psa_crypto_driver_wrappers.function | 151 /* Adjust for indirect client driver setup in first pake_output call. */
1517 /* Test setup call, encrypt */
1520 /* When setup fails, it shouldn't call any further entry points */
1528 /* Test setup call failure, decrypt */
1530 /* When setup fails, it shouldn't call any further entry points */
3074 case 0: /* setup (via input) */
3075 /* --- psa_pake_input (driver: setup, input) --- */
3082 TEST_EQUAL(mbedtls_test_driver_pake_hooks.hits.setup, 1);
3085 case 1: /* setup (via output) */
3086 /* --- psa_pake_output (driver: setup, output) --- */
[all …]
|
| D | test_suite_psa_crypto_low_hash.function | 73 mbedtls_psa_hash_operation_t clone_start; // cloned after setup
101 /* Nominal case with an operation cloned after setup */
|
| D | test_suite_psa_crypto.data | 1604 PSA hash setup: good, SHA-1
1608 PSA hash setup: good, SHA-224
1612 PSA hash setup: good, SHA-256
1616 PSA hash setup: good, SHA-384
1620 PSA hash setup: good, SHA-512
1624 PSA hash setup: good, MD5
1628 PSA hash setup: good, RIPEMD160
1632 PSA hash setup: bad (unknown hash algorithm)
1636 PSA hash setup: bad (wildcard instead of hash algorithm)
1640 PSA hash setup: bad (not a hash algorithm)
[all …]
|
| D | test_suite_psa_crypto_pake.data | 25 PSA PAKE: duplicate a valid setup
29 PSA PAKE: ecjpake setup role
|
| D | test_suite_psa_crypto.function | 172 /* Whether setup succeeded or failed, abort must succeed. */
174 /* If setup failed, reproduce the failure, so that the caller can
204 /* Whether setup succeeded or failed, abort must succeed. */
206 /* If setup failed, reproduce the failure, so that the caller can
2967 /* Whether setup succeeded or failed, abort must succeed. */
2970 /* If setup failed, reproduce the failure, so as to
3195 /* Call setup twice in a row. */
3204 /* Call update without calling setup beforehand. */
3227 /* Call verify without calling setup beforehand. */
3254 /* Call finish without calling setup beforehand. */
[all …]
|
| D | main_test.function | 246 * Note that we do this before the platform setup (which may access
|
| D | test_suite_psa_crypto_init.function | 168 /* Bad state due to entropy sources already being setup in
|
| D | test_suite_rsa.function | 1083 /* If we were providing enough information to setup a complete private context,
1235 /* If we were providing enough information to setup a complete private context,
|
| D | test_suite_pk.function | 246 * Predefined keys used for the setup are taken from "test/src/test_keys.h"
250 * (mbedtls_pk_init()), but not setup (mbedtls_pk_setup()).
2057 * The PSA key was setup to use PKCS1 v1.5 signature algorithm, but here we try
|
| D | test_suite_psa_crypto_pake.function | 570 * the pake's context structure is compromised and the setup function cannot
|
| D | test_suite_pk.data | 61 PK PSA utilities: ECDSA setup/free, info functions, unsupported operations
65 PK PSA utilities: RSA setup/free, info functions, unsupported operations
|
| /mbedtls-latest/tests/include/test/drivers/ |
| D | pake.h | 26 unsigned long setup; member
|
| /mbedtls-latest/docs/architecture/psa-migration/ |
| D | md-cipher-dispatch.md | 146 * Functions called: `setup`, `setkey`, `set_iv`, `reset`, `update`, `finish` (in sequence, once).
151 * Functions called: `setup`, `setkey`, `crypt`.
162 * Functions called: `info`, `setup`, `setkey`, `update` (several times) - (never finish)
168 * Functions called: `info`, `setup`, `setkey`, `update` (several times) - (never finish)
174 * Functions called: `info`, `setup`, `setkey`, `update` (several times) - (never finish)
181 * Functions called: `info`, `setup`, `setkey`, `update` (several times) - (never finish)
375 … check if the cipher is supported, (2) to check its block size, (3) because `setup()` requires it).
594 an `mbedtls_cipher_id_t` in the `setup()` function, because that's how they're
612 …SA or legacy. All functions consult the context's `engine` field, except `setup()` which will set …
|
| D | strategy.md | 193 There are two variants of this strategy: one where using the new setup
|
| /mbedtls-latest/tests/src/drivers/ |
| D | test_driver_pake.c | 29 mbedtls_test_driver_pake_hooks.hits.setup++; in mbedtls_test_transparent_pake_setup()
|
| /mbedtls-latest/docs/architecture/ |
| D | alternative-implementations.md | 12 …_XXX_ALT` and [register an alternative implementation during the platform setup](#alternative-impl…
|
| D | psa-shared-memory.md | 178 Key derivation typically emits its output as a stream, with no error condition detected after setup…
440 …heck that each location was accessed exactly twice: once by the program's setup and once by the PS…
475 Most of the test methods discussed above need extra setup. Some require leaking of buffer bounds, p…
|
| /mbedtls-latest/docs/proposed/ |
| D | psa-driver-interface.md | 258 …ain any embedded pointers (except pointers to global data that do not change after the setup step).
330 …rivation-driver-initial-inputs). See [“Key derivation driver setup”](#key-derivation-driver-setup).
399 … `inputs` must be a pointer passed by the core to a key derivation driver setup entry point which …
414 #### Key derivation driver setup
665 The first parameter `inputs` must be a pointer passed by the core to a PAKE driver setup entry poin…
673 #### PAKE driver setup
683 The setup driver function should preserve the inputs using get-data functions.
|
| /mbedtls-latest/docs/ |
| D | psa-transition.md | 382 If you need to interrupt the operation after calling the setup function without calling the finish …
414 If you need to interrupt the operation after calling the setup function without calling the finish …
418 …93d92318c8f592ee9fbb9d36ba0). Note that you must set the key again with a setup function: the PSA …
521 If you need to interrupt the operation after calling the setup function without calling the finish …
579 If you need to interrupt the operation after calling the setup function without calling the finish …
590 …p___m_a_c_1gacd8dd54855ba1bc0a03f104f252884fd). Note that you must call a setup function to specif…
1283 …A-ALT interface (`MBEDTLS_PK_RSA_ALT` pk type, `mbedtls_pk_setup_rsa_alt` setup function) should m…
|
| /mbedtls-latest/docs/architecture/psa-thread-safety/ |
| D | psa-thread-safety.md | 225 Multi-part and restartable operations each have a "setup" function where the key is passed in, thes…
|
| /mbedtls-latest/scripts/data_files/driver_templates/ |
| D | psa_crypto_driver_wrappers.h.jinja | 1554 /* Try setup on accelerators first */
|
| /mbedtls-latest/ |
| D | ChangeLog | 3705 * Add platform setup and teardown calls in test suites.
3863 independent setup and export of RSA contexts. Most notably,
3866 needs of the implementation automatically. This allows to setup private RSA
4007 platform-specific setup and teardown operations. The macro
6182 serial number, setup correct server port in the ssl client example
|
