Searched refs:correct (Results 1 – 18 of 18) sorted by relevance
/mbedtls-development/tests/suites/ |
A D | test_suite_cipher.padding.data | 48 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) 196 Check zeros padding #1 (correct) 200 Check zeros padding #2 (correct) 204 Check zeros padding #3 (correct) [all …]
|
A D | test_suite_pkparse.data | 1037 Key ASN1 (RSAPrivateKey, correct version, incorrect tag) 1049 Key ASN1 (RSAPrivateKey, correct format, modulus even) 1053 Key ASN1 (RSAPrivateKey, correct format, d == 0) 1065 Key ASN1 (RSAPrivateKey, correct values, n wrong tag) 1069 Key ASN1 (RSAPrivateKey, correct values, e wrong tag) 1073 Key ASN1 (RSAPrivateKey, correct values, d wrong tag) 1077 Key ASN1 (RSAPrivateKey, correct values, p wrong tag) 1081 Key ASN1 (RSAPrivateKey, correct values, q wrong tag) 1085 Key ASN1 (RSAPrivateKey, correct values, dp wrong tag) 1089 Key ASN1 (RSAPrivateKey, correct values, dq wrong tag) [all …]
|
A D | main_test.function | 130 * which the wrapper casts to the correct type and
|
A D | test_suite_ssl.function | 452 * the correct value allows for simulation of MTU, sanity testing the mock 1521 * message was sent in the correct number of fragments. 2115 * correct and works as expected. 2232 * correct and works as expected on unconnected sockets. 3580 /* Save correct pre-encryption record */ 3586 * Encrypt and decrypt the correct record, expecting success 3605 /* Restore correct pre-encryption record */ 3635 * (Start the loop with correct padding, just to double-check that record 3636 * saving did work, and that we're overwriting the correct bytes.) 3642 /* Restore correct pre-encryption record */
|
A D | test_suite_psa_crypto_se_driver_hal.function | 184 /* We're supposed to return a key size. Return one that's correct for 1052 /* Test that the key is reported with the correct attributes,
|
A D | test_suite_rsa.function | 223 data_t * result_str, int correct ) 244 …kcs1_verify( &ctx, MBEDTLS_MD_NONE, hash_result->len, hash_result->x, result_str->x ) == correct );
|
A D | test_suite_x509parse.data | 2015 X509 CRL ASN1 (TBSCertList, version correct, alg missing) 2018 X509 CRL ASN1 (TBSCertList, alg correct, incorrect version) 2021 X509 CRL ASN1 (TBSCertList, correct version, sig_oid1 unknown) 2027 X509 CRL ASN1 (TBSCertList, sig_oid1 correct, issuer missing) 2035 X509 CRL ASN1 (TBSCertList, correct issuer, thisUpdate missing) 2039 X509 CRL ASN1 (TBSCertList, correct thisUpdate, nextUpdate missing, entries length missing)
|
A D | test_suite_ecp.function | 516 * Store correct result before we touch N
|
A D | test_suite_psa_crypto.function | 1157 /* Verify correct MAC, one-shot case. */ 1906 /* Compare with correct hash */ 2496 /* Verify correct MAC, one-shot case. */ 2500 /* Verify correct MAC, multi-part case. */ 5181 /* Use the library to verify that the signature is correct. */
|
A D | test_suite_psa_crypto.data | 3762 PSA verify hash: ECDSA SECP256R1, wrong signature size (correct but ASN1-encoded) 3766 PSA verify hash: ECDSA SECP256R1, wrong signature of correct size 4010 PSA verify message: ECDSA SECP256R1, wrong signature size (correct but ASN1-encoded) 4014 PSA verify message: ECDSA SECP256R1, wrong signature of correct size
|
/mbedtls-development/library/ |
A D | ssl_msg.c | 1208 size_t padlen = 0, correct = 1; in mbedtls_ssl_decrypt_buf() local 1526 correct &= mask; in mbedtls_ssl_decrypt_buf() 1546 correct &= mask; in mbedtls_ssl_decrypt_buf() 1582 correct &= mbedtls_ssl_cf_bool_eq( pad_count, padlen ); in mbedtls_ssl_decrypt_buf() 1585 if( padlen > 0 && correct == 0 ) in mbedtls_ssl_decrypt_buf() 1588 padlen &= mbedtls_ssl_cf_mask_from_bit( correct ); in mbedtls_ssl_decrypt_buf() 1679 correct = 0; in mbedtls_ssl_decrypt_buf() 1687 if( correct == 0 ) in mbedtls_ssl_decrypt_buf()
|
/mbedtls-development/ |
A D | CONTRIBUTING.md | 47 1. All bug fixes that correct a defect that is also present in an LTS branch must be backported to …
|
A D | ChangeLog | 1336 incoming record with the correct connection data even after the peer has 2104 with flag MBEDTLS_X509_BADCERT_BAD_PK even when the key type was correct. 2119 * Log correct number of ciphersuites used in Client Hello message. #918 2317 structure. Do not assume that zeroizing a context is a correct way to 3972 * Server not always sending correct CertificateRequest message 4151 * Fixed generation of DHM parameters to correct length (found by Ruslan 4536 serial number, setup correct server port in the ssl client example
|
/mbedtls-development/docs/architecture/testing/ |
A D | driver-interface-test-strategy.md | 56 …n a test that checks the outputs if the only realistic way to obtain the correct outputs is to sta…
|
A D | invasive-testing.md | 111 …to test resilience: if the system is reset during an operation, does it restart in a correct state?
|
/mbedtls-development/docs/proposed/ |
A D | psa-driver-interface.md | 217 …l for drivers of secure elements that verify a MAC without revealing the correct MAC. Although tra… 356 …port_key"` entry point must set the `bits` input-output parameter to the correct key size. The sem…
|
/mbedtls-development/docs/ |
A D | 3.0-migration-guide.md | 438 The migration path is to pass the correct value to those functions.
|
/mbedtls-development/doxygen/ |
A D | mbedtls.doxyfile | 1464 # would be unable to find the correct page. The default is NO.
|
Completed in 71 milliseconds