Home
last modified time | relevance | path

Searched refs:correct (Results 1 – 25 of 36) sorted by relevance

12

/mbedtls-latest/tests/suites/
Dtest_suite_cipher.padding.data48 Check PKCS padding #1 (correct)
52 Check PKCS padding #2 (correct)
56 Check PKCS padding #3 (correct)
60 Check PKCS padding #4 (correct)
140 Check one and zeros padding #1 (correct)
144 Check one and zeros padding #2 (correct)
148 Check one and zeros padding #3 (correct)
152 Check one and zeros padding #4 (correct)
156 Check one and zeros padding #5 (correct)
172 Check zeros and len padding #1 (correct)
[all …]
Dtest_suite_bignum_core.function35 /* A + B => correct result and carry */
39 /* A + B; alias output and first operand => correct result and carry */
44 /* A + B; alias output and second operand => correct result and carry */
52 /* A + A => correct result and carry */
56 /* A + A, output aliased to both operands => correct result and carry */
63 /* B + A => correct result and carry */
67 /* B + A; alias output and first operand => correct result and carry */
72 /* B + A; alias output and second operand => correct result and carry */
116 /* cond = 1 => correct result and carry */
128 /* cond = 1 => correct result and carry */
[all …]
Dtest_suite_rsa.data742 RSA parse private key - correct version, incorrect tag
745 RSA parse private key - correct format+values, minimal modulus size (128 bit)
751 RSA parse private key - correct format, modulus too small (127 bit)
754 RSA parse private key - correct format, modulus even
757 RSA parse private key - correct format, d == 0
760 RSA parse private key - correct format, d == p == q == 0
763 RSA parse private key - correct values, extra integer inside the SEQUENCE
766 RSA parse private key - correct values, extra integer outside the SEQUENCE
769 RSA parse private key - correct values, n wrong tag
772 RSA parse private key - correct values, e wrong tag
[all …]
Dtest_suite_ssl_decrypt.function226 /* Save correct pre-encryption record */
232 * Encrypt and decrypt the correct record, expecting success
249 /* Restore correct pre-encryption record */
278 * (Start the loop with correct padding, just to double-check that record
279 * saving did work, and that we're overwriting the correct bytes.)
284 /* Restore correct pre-encryption record */
Dtest_suite_ecdsa.data413 ECDSA verify valid public key, correct sig, 0 bytes of data
417 ECDSA verify valid pub key, correct sig, 1 byte of data
421 ECDSA verify valid pub key, correct sig, 32 bytes of data
Dtest_suite_psa_crypto_memory.function15 * important, it just allows a basic check that the correct thing has
Dtest_suite_lms.data70 # * hsslms sign tmp/lms.prv message.bin (correct signature using leaf node 2)
129 # * <hash-sigs>/demo sign tmp/lms message.bin (correct signature using leaf node 1)
Dmain_test.function128 * which the wrapper casts to the correct type and
Dtest_suite_alignment.function337 /* Verify write - check memory is correct */
Dtest_suite_md.function52 /* Check that this OID definition maps back to the correct mbedtls_md_type_t */
Dtest_suite_pk.function2067 /* Perform sign_ext() with the correct pk_type. */
2599 /* - Check that the generated PK contexts are of the correct type.
2600 * - [Only for RSA] check that the padding mode is correct.
2690 * the result is correct. */
Dtest_suite_psa_crypto.function1360 * PSA_ERROR_INSUFFICIENT_MEMORY; this is correct behaviour.
1606 * NOT_SUPPORTED which is correct at this point;
1608 * NOT_SUPPORTED which again is correct at this point.
2200 /* Verify correct MAC, one-shot case. */
2210 /* Verify correct MAC, multi-part case. */
3121 /* Compare with correct hash, one-shot */
3125 /* Compare with correct hash, multi-part */
3782 /* Verify correct MAC, one-shot case. */
3786 /* Verify correct MAC, multi-part case. */
7023 * correct error codes, and at the correct point (at start or during
[all …]
Dtest_suite_psa_crypto_se_driver_hal.function200 /* We're supposed to return a key size. Return one that's correct for
1073 /* Test that the key is reported with the correct attributes,
Dtest_suite_rsa.function294 data_t *result_str, int correct)
317 result_str->x) == correct);
Dtest_suite_x509write.function599 // Check correct tag and time written
Dtest_suite_bignum_mod.function492 /* Allocate correct number of limbs for X_raw */
Dtest_suite_bignum_mod_raw.function507 * to see if the output is correct, but we can check that it's in a
/mbedtls-latest/scripts/
Dci.requirements.txt15 # It needs >=35.0.0 for correct operation, and that requires Python >=3.6,
/mbedtls-latest/library/
Dssl_msg.c1492 mbedtls_ct_condition_t correct = MBEDTLS_CT_TRUE; in mbedtls_ssl_decrypt_buf() local
1916 correct = mbedtls_ct_bool_and(ge, correct); in mbedtls_ssl_decrypt_buf()
1932 correct = mbedtls_ct_bool_and(ge, correct); in mbedtls_ssl_decrypt_buf()
1968 correct = mbedtls_ct_bool_and(mbedtls_ct_uint_eq(pad_count, padlen), correct); in mbedtls_ssl_decrypt_buf()
1971 if (padlen > 0 && correct == MBEDTLS_CT_FALSE) { in mbedtls_ssl_decrypt_buf()
1975 padlen = mbedtls_ct_size_if_else_0(correct, padlen); in mbedtls_ssl_decrypt_buf()
2073 correct = MBEDTLS_CT_FALSE; in mbedtls_ssl_decrypt_buf()
2088 if (correct == MBEDTLS_CT_FALSE) { in mbedtls_ssl_decrypt_buf()
/mbedtls-latest/docs/architecture/
Dpsa-storage-resilience.md5 …rage exhibits non-nominal behavior. In this document, _resilience_ means correct behavior of the k…
324 …* It is correct to destroy the key in the secure element (treating a `DOES_NOT_EXIST` error as a s…
325 …* It is correct to check whether the key exists in the secure element, and if it does, keep it and…
340 …* It is correct to destroy the key in the secure element (treating a `DOES_NOT_EXIST` error as a s…
341 …* It is correct to check whether the key exists in the secure element, and if it does, keep it and…
453 It is correct to update the transaction list after recovering each key, or to only delete the trans…
Dpsa-shared-memory.md248 …ortant platforms while retaining a C implementation that is likely to be correct on most platforms…
330 …test cases that call PSA functions on incorrect inputs to check that the correct error is returned…
361 …soned straight after the function returns, so that they can be read to check the output is correct.
/mbedtls-latest/docs/architecture/psa-thread-safety/
Dpsa-thread-safety.md43 Building with `MBEDTLS_PSA_CRYPTO_C` and `MBEDTLS_THREADING_C` gives code which is correct; there a…
239 … this error. Even if such an error occurs, all calls are still required to be functionally correct.
255 … multiple threads fail a test assert, the first failure will be reported with correct line numbers.
/mbedtls-latest/docs/architecture/testing/
Ddriver-interface-test-strategy.md56 …n a test that checks the outputs if the only realistic way to obtain the correct outputs is to sta…
/mbedtls-latest/
DCONTRIBUTING.md48 1. All bug fixes that correct a defect that is also present in an LTS branch must be backported to …
/mbedtls-latest/docs/
Dpsa-driver-example-and-guide.md83 * `PSA_ERROR_NOT_SUPPORTED`: Input arguments are correct, but the driver does not support the opera…

12