Searched refs:valid (Results 1 – 25 of 46) sorted by relevance
12
| /mbedtls-latest/tests/suites/ |
| D | test_suite_lmots.data | 90 # This test uses the valid signature from hsslms interop test 1, and then
96 # This test uses the valid signature from hsslms interop test 1, and then
102 # This test uses the valid signature from hsslms interop test 1, and then
108 # This test uses the valid public key for hsslms interop test 1, imports it, and
114 # This test uses the valid public key for hsslms interop test 1, add an extra
119 # This test uses the valid public key for hsslms interop test 1, removes a byte,
124 # This test uses the valid public key for hsslms interop test 1, cuts it down so
130 # This test uses the valid public key for hsslms interop test 1, alters the
135 # This test uses the valid public key for hsslms interop test 1, alters the
|
| D | test_suite_ecdsa.data | 389 ECDSA verify valid pub key, invalid sig (r=0), 0 bytes of data
393 ECDSA verify valid pub key, invalid sig (r=0), 1 byte of data
397 ECDSA verify valid pub key, invalid sig (r>n-1), 32 bytes of data
401 ECDSA verify valid pub key, valid/incorrect sig, 0 bytes of data
405 ECDSA verify valid pub key, valid/incorrect sig, 1 byte of data
409 ECDSA verify valid pub key, valid/incorrect sig, 32 bytes of data
413 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
|
| D | test_suite_lms.data | 190 # This test uses the data from hash-sigs interop test #1. This test has a valid
195 # This test uses the data from hash-sigs interop test #1. This test has a valid
201 # invalid LMOTS type (0x3) but a valid LMS type (0x6), and should fail.
206 # invalid LMOTS type (0x5) but a valid LMS type (0x6), and should fail.
222 # This test uses the valid public key for hsslms interop test 1, add an extra
227 # This test uses the valid public key for hsslms interop test 1, removes a byte,
232 # This test uses the valid public key for hsslms interop test 1, cuts it down so
238 # This test uses the valid public key for hsslms interop test 1, cuts it down so
244 # This test uses the valid public key for hsslms interop test 1, alters the
249 # This test uses the valid public key for hsslms interop test 1, alters the
[all …]
|
| D | test_suite_base64.data | 162 Base64 encode hex all valid input bytes #0
165 Base64 encode hex all valid input bytes #1
168 Base64 encode hex all valid input bytes #2
171 Base64 encode all valid output characters at all offsets
189 Base64 decode all valid input characters at all offsets
|
| D | test_suite_pk.data | 4 PK valid parameters
7 PK write valid parameters
1558 Copy from PSA: valid EC (SECP_R1_256 + ECDSA + ANY_HASH)
1562 Copy from PSA: valid EC (SECP_R1_256 + ECDSA + SHA_256)
1566 Copy from PSA: valid EC (SECP_R1_256 + ECDSA + SHA_512)
1570 Copy from PSA: valid EC (SECP_R1_256 + DET_ECDSA + ANY_HASH)
1574 Copy from PSA: valid EC (SECP_R1_256 + DET_ECDSA + SHA_256)
1578 Copy from PSA: valid EC (SECP_R1_256 + DET_ECDSA + SHA_512)
1582 Copy from PSA: valid EC (SECP_R1_256 + ECDSA_ANY)
1586 Copy from PSA: valid EC (SECP_R1_521 + ECDSA + SHA_256)
[all …]
|
| D | test_suite_ecjpake.data | 10 ECJPAKE round one: client, valid
13 ECJPAKE round one: server, valid
118 ECJPAKE round two client: valid
184 ECJPAKE round two server: valid
|
| D | test_suite_x509parse.data | 494 # Parse the following valid DN:
838 X509 CRT verification #52 (CA keyUsage valid)
962 X509 CRT verification #82 (Not yet valid CA and valid CA)
966 X509 CRT verification #83 (valid CA and Not yet valid CA)
970 X509 CRT verification #84 (valid CA and Not yet valid CA)
974 X509 CRT verification #85 (Not yet valid CA and valid CA)
978 X509 CRT verification #86 (Not yet valid CA and invalid CA)
1082 X509 CRT parse CN: IPv4 valid address
1127 X509 CRT parse CN: IPv6 valid address
1130 X509 CRT parse CN: IPv6 valid address shorthand
[all …]
|
| D | test_suite_pem.data | 22 PEM read (unencrypted, valid)
59 PEM read (valid EC key encoded with AES-128-CBC)
|
| D | test_suite_block_cipher.function | 28 /* That size is valid for a key or an input/output block. */
|
| D | test_suite_asn1parse.function | 37 /* Since we have a valid element start (tag and length), retrieve and
234 * valid depending on what the trailing garbage is. */
335 /* An INTEGER with no content is not valid. */
|
| D | test_suite_psa_crypto_metadata.function | 102 * possibly turn a valid encoding into another valid encoding. Here in
106 * The expected parity is even so that 0 is considered a valid encoding.
|
| D | test_suite_net.function | 113 /* In principle, mbedtls_net_poll() with valid arguments should succeed.
|
| D | test_suite_lms.function | 91 /* Test negative cases if the input data is valid */
|
| D | test_suite_bignum.function | 18 /* Only +1 and -1 are valid sign bits, not e.g. 0 */
1280 * is a valid value. However, negating it (`-n`) has undefined behavior
1402 /* Test mbedtls_mpi_mod_int(): never valid */
1406 /* Test mbedtls_mpi_random(): never valid */
|
| D | test_suite_lmots.function | 91 /* Test negative cases if the input data is valid */
|
| D | host_test.function | 88 /* Read until we get a valid line */
268 * only. They are still valid for other compilers. Avoid this warning by
|
| D | test_suite_ssl.data | 3115 Version config: valid client TLS 1.2 only
3119 Version config: valid client DTLS 1.2 only
3123 Version config: valid server TLS 1.2 only
3127 Version config: valid server DTLS 1.2 only
3147 Version config: valid client TLS 1.3 only
3155 Version config: valid server TLS 1.3 only
3179 Version config: valid client hybrid TLS 1.2/3
3187 Version config: valid server hybrid TLS 1.2/3
3195 Version config: valid client hybrid TLS 1.2/3, no TLS 1.2
3203 Version config: valid server hybrid TLS 1.2/3, no TLS 1.2
[all …]
|
| D | test_suite_psa_crypto_pake.data | 25 PSA PAKE: duplicate a valid setup
|
| D | test_suite_md.function | 30 * Test that mbedtls_md_list() only returns valid MDs.
|
| D | test_suite_ssl.function | 109 * error if the length is not zero, and that a NULL output is valid for data
200 /* In order to always have a valid pointer we always allocate at least 1
214 /* In order to always have a valid pointer we always allocate at least 1
929 /* Test that the first half of the message is valid, and second one isn't */
940 /* Test that the first half of the message is valid */
991 /* Return to a valid state */
3521 /* check that the opaque key is still valid after failure */
|
| /mbedtls-latest/library/ |
| D | constant_time.c | 137 mbedtls_ct_condition_t valid = mbedtls_ct_bool_and(mbedtls_ct_uint_ge(i, skip_head), in mbedtls_ct_memcmp_partial() local
139 diff |= mbedtls_ct_uint_if_else_0(valid, d); in mbedtls_ct_memcmp_partial()
|
| /mbedtls-latest/doxygen/ |
| D | mbedtls.doxyfile | 37 # This is perfectly valid as far as Doxygen is concerned. However, with
|
| /mbedtls-latest/docs/architecture/ |
| D | psa-crypto-implementation-structure.md | 26 * checking PSA API arguments and translating them into valid arguments for the necessary calls to t…
159 * Attempt to perform an operation with a combination of key type and algorithm that is not valid or…
165 * `framework/scripts/mbedtls_framework/asymmetric_key_data.py` contains valid key data for asymmetr…
|
| D | alternative-implementations.md | 64 In practice, this means that a pointer to a context or to a part of a context does not remain valid…
|
| /mbedtls-latest/docs/proposed/ |
| D | psa-driver-interface.md | 77 * `"prefix"` (mandatory, string). This must be a valid, non-empty prefix for a C identifier. All th…
373 * `PSA_KEY_DERIVATION_INPUT_TYPE_BYTES`: the step is valid and present and is a transparent byte st…
374 * `PSA_KEY_DERIVATION_INPUT_TYPE_KEY`: the step is valid and present and is a byte string passed vi…
375 * `PSA_KEY_DERIVATION_INPUT_TYPE_INTEGER`: the step is valid and present and is an integer. Call `p…
403 …` to the size of the key context in bytes. The key context buffer remains valid for the duration o…
409 * `PSA_ERROR_DOES_NOT_EXIST`: the input step is valid for this particular algorithm, but it is not …
685 The pointer output by `psa_crypto_driver_pake_get_password_key` is only valid until the "pake_setup…
785 All key creation entry points must ensure that the resulting key is valid as specified in the secti…
801 …valid key data. Key data is _valid_ if operations involving the key are guaranteed to work functio…
806 * On the other hand, it is acceptable for import to accept a key that cannot be verified as valid i…
[all …]
|
12
