Searched refs:success (Results 1 – 25 of 27) sorted by relevance
12
| /mbedtls-latest/tests/scripts/ |
| D | run_demos.py | 27 success = run_demo(demo, quiet=quiet)
28 if not success:
33 print('{}: {}'.format(demo, 'PASS' if success else 'FAIL'))
59 success = run_all_demos(quiet=options.quiet)
60 sys.exit(0 if success else 1)
|
| D | depends.py | 199 success = True
211 success = False
213 return success
454 success = job.test(options)
455 job.announce(colors, success)
456 return success
474 success = run(options, job, conf, colors=colors)
475 if not success:
|
| /mbedtls-latest/tests/suites/ |
| D | host_test.function | 9 * \return 0 if success else 1
33 * \return 0 if success else 1
81 * \return 0 if success else -1
202 * \return 0 for success else 1
275 * \return 0 for success else 1
306 * \return 0 for success else 1
|
| D | test_suite_net.function | 28 * On success, it refers to the opened file (\p wanted_fd).
31 * \return \c 0 on success, a negative error code on error.
|
| D | test_suite_mps.function | 1003 int success = 0;
1030 success = 1;
1039 success = 1;
1071 success = 1;
1083 success = 1;
1095 success = 1;
1108 success = 1;
1116 if (success == 1) {
|
| D | test_suite_psa_crypto_generate_key.function | 32 // Verify attributes of the created key on success
|
| D | test_suite_psa_crypto_storage_format.function | 17 * mark the test case as failed and return 0. On success, return 1.
143 * mark the test case as failed and return 0. On success, return 1.
|
| D | test_suite_psa_crypto_se_driver_hal_mocks.data | 1 SE init mock test: success
|
| D | test_suite_bignum_random.function | 173 /* They must return the same status, and, on success, output the
233 /* They must return the same status, and, on success, output the
|
| D | test_suite_pkparse.function | 57 * For now, for such keys, treat not-supported from PSA as a success.
|
| D | test_suite_rsa.function | 144 * already been called in the success path. */
946 /* On expected success, perform some public and private
1336 /* On expected success, perform some public and private
|
| D | test_suite_ssl_decrypt.function | 232 * Encrypt and decrypt the correct record, expecting success
|
| D | test_suite_entropy.function | 158 * checking whether it has already been called in the success path. */
|
| D | test_suite_aes.function | 105 // expected result is always success on zero-length input, so skip len == 0 if expecting failure
|
| D | test_suite_psa_crypto_driver_wrappers.data | 865 PSA PAKE: ecjpake rounds transparent driver: in-driver success
869 PSA PAKE: ecjpake rounds transparent driver: fallback success
|
| D | test_suite_psa_crypto_pake.function | 546 * - in case of success following functions depend on the current one
|
| D | test_suite_cipher.function | 636 * return success, not MBEDTLS_ERR_CIPHER_FULL_BLOCK_EXPECTED, when
|
| D | test_suite_pk.function | 255 * \return 0 on success or a negative value otherwise.
|
| /mbedtls-latest/docs/architecture/ |
| D | psa-storage-resilience.md | 213 1. Remove the key file, treating `DOES_NOT_EXIST` as a success.
214 2. Call the driver's `"destroy_key"` entry point, treating `DOES_NOT_EXIST` as a success.
239 2. Call the driver's `"destroy_key"` entry point, treating `DOES_NOT_EXIST` as a success.
240 3. Remove the key file, treating `DOES_NOT_EXIST` as a success.
324 …oy the key in the secure element (treating a `DOES_NOT_EXIST` error as a success), then remove `id…
338 …exist, then destroy the key in the secure element (treating a `DOES_NOT_EXIST` error as a success).
340 …oy the key in the secure element (treating a `DOES_NOT_EXIST` error as a success), then remove `id…
387 …nt's key destruction entry point (treating a `DOES_NOT_EXIST` error as a success), then remove `id…
520 2. Call `psa_crypto_init()`. Expect success if the initial state satisfies the [storage invariant](…
521 3. On success, check that the expected keys exist, and that keys that are expected to have been des…
|
| D | psa-shared-memory.md | 575 …loc()`. On failure, it sets an error code and jumps to an exit label. On success, it sets `input_c…
|
| /mbedtls-latest/library/ |
| D | x509_crt.c | 1399 int success = 0, first_error = 0, total_failed = 0; in mbedtls_x509_crt_parse() local
1490 success = 1; in mbedtls_x509_crt_parse()
1494 if (success) { in mbedtls_x509_crt_parse()
|
| /mbedtls-latest/docs/proposed/ |
| D | psa-driver-interface.md | 532 * On success, `*key_buffer_length` must contain the number of bytes written to `key_buffer`.
754 * `output_length` On success, the number of bytes of the implicit key.
832 …_bits`: on success, an estimate of the amount of entropy that is present in the `output` buffer, i…
833 * `output`: on success, this buffer contains non-deterministic data with an estimated entropy of at…
840 * `PSA_SUCCESS`: success. The output buffer contains some entropy.
1006 * `output`: on success (including partial success), the first `*output_length` bytes of this buffer…
1008 * `*output_length`: on success (including partial success), the number of bytes of random data that…
1251 …utes` with the attributes of the key (except for the key identifier). On success, this function mu…
|
| /mbedtls-latest/docs/architecture/psa-thread-safety/ |
| D | psa-thread-safety.md | 208 …), sets the slot's state to `PSA_SLOT_FULL` and releases the mutex. Upon success, any thread is im…
245 … The linearization point is the mutex unlock after wiping the slot for a success, or unregistering…
|
| /mbedtls-latest/docs/architecture/testing/ |
| D | invasive-testing.md | 306 #### PSA storage cleanup on success
|
| /mbedtls-latest/docs/ |
| D | psa-transition.md | 74 Mbed TLS functions return a status of type `int`: 0 for success (or occasionally a positive value w…
76 …roup__error_1ga05676e70ba5c6a7565aff3c36677c1f9): `PSA_SUCCESS == 0` for success, or a negative va…
|
12
