| /openthread-latest/third_party/mbedtls/repo/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 | 633 Hash multi-part setup: SHA-256, computed by the driver
637 Hash multi-part setup: SHA-256, fallback
641 Hash multi-part setup: SHA-256, no fallback
645 Hash multi-part setup: SHA-256, INSUFFICIENT_MEMORY
800 PSA AEAD encrypt setup, AES-GCM, 128 bytes #1
804 PSA AEAD encrypt setup, AES-GCM, 128 bytes #1, fallback
808 PSA AEAD encrypt setup, AES-GCM, 128 bytes #1, INSUFFICIENT_MEMORY
812 PSA AEAD decrypt setup, AES-GCM, 144 bytes #1
816 PSA AEAD decrypt setup, AES-GCM, 144 bytes #1, fallback
820 PSA AEAD decrypt setup, AES-GCM, 144 bytes #1, insufficient memory
[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_driver_wrappers.function | 151 /* Adjust for indirect client driver setup in first pake_output call. */
1501 /* Test setup call, encrypt */
1504 /* When setup fails, it shouldn't call any further entry points */
1512 /* Test setup call failure, decrypt */
1514 /* When setup fails, it shouldn't call any further entry points */
3058 case 0: /* setup (via input) */
3059 /* --- psa_pake_input (driver: setup, input) --- */
3066 TEST_EQUAL(mbedtls_test_driver_pake_hooks.hits.setup, 1);
3069 case 1: /* setup (via output) */
3070 /* --- psa_pake_output (driver: setup, output) --- */
[all …]
|
| 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 | main_test.function | 246 * Note that we do this before the platform setup (which may access
|
| D | test_suite_psa_crypto_init.function | 151 /* Bad state due to entropy sources already being setup in
|
| D | test_suite_psa_crypto.function | 194 /* Whether setup succeeded or failed, abort must succeed. */
196 /* If setup failed, reproduce the failure, so that the caller can
226 /* Whether setup succeeded or failed, abort must succeed. */
228 /* If setup failed, reproduce the failure, so that the caller can
2987 /* Whether setup succeeded or failed, abort must succeed. */
2990 /* If setup failed, reproduce the failure, so as to
3215 /* Call setup twice in a row. */
3224 /* Call update without calling setup beforehand. */
3247 /* Call verify without calling setup beforehand. */
3274 /* Call finish without calling setup beforehand. */
[all …]
|
| 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,
|
| /openthread-latest/script/ |
| D | check-size | 69 setup() function
365 setup
368 elif [[ $1 == setup ]]; then
369 setup
|
| /openthread-latest/tools/otci/ |
| D | setup.py | 34 setuptools.setup(
|
| /openthread-latest/tools/harness-sniffer/ |
| D | README.md | 14 python setup.py install
|
| /openthread-latest/third_party/mbedtls/repo/tests/include/test/drivers/ |
| D | pake.h | 26 unsigned long setup; member
|
| /openthread-latest/third_party/mbedtls/repo/tests/src/drivers/ |
| D | test_driver_pake.c | 29 mbedtls_test_driver_pake_hooks.hits.setup++; in mbedtls_test_transparent_pake_setup()
|
| /openthread-latest/tools/harness-simulation/ |
| D | README.md | 7 …s, which is a non-POSIX environment. So two systems are needed, and their setup procedures in deta…
|
| /openthread-latest/third_party/mbedtls/repo/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 …
|
| /openthread-latest/tools/harness-simulation/posix/etc/ |
| D | Dockerfile | 102 && ./script/setup \
|
| /openthread-latest/tools/harness-thci/ |
| D | README.md | 42 …ig\Configuration.ini`. See https://openthread.io/certification/automation-setup#acting_as_a_new_re…
|
| /openthread-latest/src/cli/ |
| D | README_COAP.md | 13 On node 1, setup CoAP server with resource `test-resource`.
|
| D | README_COAPS.md | 33 On node 1, setup CoAPS server with resource `test-resource`.
|
| /openthread-latest/third_party/mbedtls/repo/docs/architecture/ |
| D | alternative-implementations.md | 12 …_XXX_ALT` and [register an alternative implementation during the platform setup](#alternative-impl…
|
| /openthread-latest/ |
| D | CONTRIBUTING.md | 9 - [4.1 Initial Setup](#initial-setup)
|
| /openthread-latest/third_party/mbedtls/repo/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.
|
| /openthread-latest/third_party/mbedtls/repo/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…
|
