Home
last modified time | relevance | path

Searched refs:algorithm (Results 1 – 24 of 24) sorted by relevance

/openthread-3.6.0/third_party/mbedtls/repo/include/psa/
Dcrypto_se_driver.h187 psa_algorithm_t algorithm);
393 psa_algorithm_t algorithm,
492 psa_algorithm_t algorithm,
737 psa_algorithm_t algorithm,
779 psa_algorithm_t algorithm,
/openthread-3.6.0/third_party/mbedtls/repo/library/
Dpsa_crypto_invasive.h82 psa_algorithm_t algorithm,
Dpsa_crypto.c563 psa_algorithm_t algorithm, in psa_mac_key_can_do() argument
566 if( PSA_ALG_IS_HMAC( algorithm ) ) in psa_mac_key_can_do()
572 if( PSA_ALG_IS_BLOCK_CIPHER_MAC( algorithm ) ) in psa_mac_key_can_do()
/openthread-3.6.0/third_party/mbedtls/repo/tests/suites/
Dtest_suite_psa_crypto_entropy.data5 # implementation of the algorithm that uses randomization, whether it's
6 # because the algorithm is randomized or because our implementation uses
Dtest_suite_psa_crypto_se_driver_hal_mocks.function578 psa_algorithm_t algorithm = PSA_ALG_ECDSA(PSA_ALG_SHA_256);
604 psa_set_key_algorithm( &attributes, algorithm );
611 TEST_ASSERT( psa_sign_hash( id, algorithm,
639 psa_algorithm_t algorithm = PSA_ALG_ECDSA(PSA_ALG_SHA_256);
664 psa_set_key_algorithm( &attributes, algorithm );
671 TEST_ASSERT( psa_verify_hash( id, algorithm,
Dtest_suite_psa_crypto_generate_key.function21 // key lifetiem, usage flags, algorithm are irrelevant for this test
Dtest_suite_psa_crypto.data431 PSA key policy: MAC, wrong algorithm
487 PSA key policy: HMAC, sign-verify, min-length policy, unmatched base alg (different algorithm)
491 PSA key policy: HMAC, sign-verify, min-length policy used as algorithm
511 PSA key policy: cipher, wrong algorithm
535 PSA key policy: AEAD, wrong algorithm
595 PSA key policy: AEAD, min-length policy used as algorithm
615 PSA key policy: asymmetric encryption, wrong algorithm (v1.5/OAEP)
619 PSA key policy: asymmetric encryption, wrong algorithm (OAEP with different hash)
695 PSA key policy: asymmetric signature, wrong hash algorithm
743 PSA key policy: msg asymmetric signature, wrong hash algorithm
[all …]
Dtest_suite_psa_crypto_metadata.function14 /* Flags for algorithm classification macros. There is a flag for every
15 * algorithm classification macro PSA_ALG_IS_xxx except for the
320 /* Check that calling PSA_ALG_TRUNCATED_MAC on an algorithm
352 /* Check that calling PSA_ALG_AT_LEAST_THIS_LENGTH_MAC on an algorithm
447 /* Check that calling PSA_ALG_AEAD_WITH_SHORTENED_TAG on an algorithm
481 * algorithm earlier constructed with PSA_ALG_AEAD_WITH_SHORTENED_TAG
Dtest_suite_pem.data25 PEM read (unknown encryption algorithm)
Dtest_suite_psa_crypto_slot_management.data189 Copy persistent to persistent with enrollment algorithm
Dtest_suite_psa_crypto_driver_wrappers.function171 /* In the builtin algorithm the driver is called twice. */
229 /* In the builtin algorithm the driver is called twice. */
Dtest_suite_x509parse.function635 TEST_ASSERT( "Unknown algorithm profile" == 0 );
Dtest_suite_x509parse.data1472 X509 CRT ASN1 (TBS, inv SubPubKeyInfo, inv algorithm tag)
1476 X509 CRT ASN1 (TBS, inv SubPubKeyInfo, algorithm length missing)
1480 X509 CRT ASN1 (TBS, inv SubPubKeyInfo, algorithm inv length encoding)
1484 X509 CRT ASN1 (TBS, inv SubPubKeyInfo, algorithm length out of bounds)
1488 X509 CRT ASN1 (TBS, inv SubPubKeyInfo, algorithm empty)
1492 X509 CRT ASN1 (TBS, inv SubPubKeyInfo, algorithm unknown)
Dtest_suite_psa_crypto.function288 /* Check that the length for a truncated MAC always fits in the algorithm
290 * untruncated algorithm may be one byte larger. */
Dtest_suite_ssl.function868 * \p pk_alg the algorithm to use, currently only MBEDTLS_PK_RSA and
/openthread-3.6.0/third_party/mbedtls/repo/docs/architecture/
Dmbed-crypto-storage-specification.md57 * policy usage algorithm (4 bytes): `psa_algorithm_t` value
189 * policy usage algorithm (4 bytes): `psa_algorithm_t` value
190 * policy enrollment algorithm (4 bytes): `psa_algorithm_t` value [NEW:1.1.0]
249 * policy usage algorithm (4 bytes): `psa_algorithm_t` value.
250 * policy enrollment algorithm (4 bytes): `psa_algorithm_t` value.
309 * policy usage algorithm (4 bytes): `psa_algorithm_t` value.
310 * policy enrollment algorithm (4 bytes): `psa_algorithm_t` value.
/openthread-3.6.0/third_party/mbedtls/repo/docs/proposed/
Dpsa-conditional-inclusion-c.md101 …A_ALG_xxx`, the symbol **`PSA_WANT_ALG_xxx`** indicates that support for this algorithm is desired.
176 An entry point can be eliminated entirely if no algorithm requires it.
196 …algorithm, include a capability with that algorithm, the key types that apply to that algorithm, n…
222 …mandate a compile-time error if a key type is required, but no matching algorithm, or vice versa? …
228 This is especially relevant to suppress a mechanism completely if there is no matching algorithm. F…
Dpsa-driver-interface.md22 … is available for a particular combination of parameters (cryptographic algorithm, key type and si…
89 …orithms"` (optional, list of strings). Each element is an [algorithm specification](#algorithm-spe…
102 * If the mechanism involves an algorithm:
104 …`"algorithms"` property includes an [algorithm specification](#algorithm-specifications) that matc…
110 …property includes a [key type specification](#key-type-specifications) that matches this algorithm.
115 …algorithm, key type and key size, and all the capabilities map the entry point to the same functio…
117 …rs have applicable capabilities for a given combination of entry point, algorithm, key type and ke…
123 …nistic ECDSA signatures (but not signature verification) using any hash algorithm and any curve th…
146 …algorithm specification is a string consisting of a `PSA_ALG_xxx` macro that specifies a cryptogra…
160 An algorithm specification is a string consisting of a `PSA_KEY_TYPE_xxx` macro that specifies a ke…
[all …]
Dpsa-driver-developer-guide.md20 … is available for a particular combination of parameters (cryptographic algorithm, key type and si…
/openthread-3.6.0/third_party/mbedtls/repo/docs/
Dgetting_started.md124 * Algorithm set to the desired signature algorithm.
196 1. Call `psa_cipher_encrypt_setup()` to specify the algorithm and the key to be used.
280 1. Call `psa_cipher_decrypt_setup()` to specify the algorithm and the key to be used.
388 1. Call `psa_hash_setup()` to specify the hash algorithm.
485 …o `PSA_HASH_LENGTH`, which returns the expected hash length (in bytes) for the specified algorithm.
548 See the documentation for the particular algorithm (such as HKDF or the TLS1.2 PRF) for
556 * Algorithm set to a key derivation algorithm
563 function, specifying the derivation algorithm `PSA_ALG_HKDF(PSA_ALG_SHA_256)`.
569 the `PSA_KEY_USAGE_ENCRYPT` usage flag and the `PSA_ALG_CTR` algorithm for this
678 …ay to authenticate and encrypt with associated data (AEAD), supporting the `PSA_ALG_CCM` algorithm.
[all …]
/openthread-3.6.0/third_party/mbedtls/repo/programs/
DREADME.md38 …SA private/public key and uses it to sign/verify a short string with the RSA PKCS#1 v1.5 algorithm.
40 … an RSA private/public key and uses it to sign/verify a short string with the RSASSA-PSS algorithm.
/openthread-3.6.0/third_party/mbedtls/repo/
DChangeLog83 This algorithm now accepts only the same salt length for verification
84 that it produces when signing, as documented. Use the new algorithm
87 for algorithm values that fully encode the hashing step, as per the PSA
259 that PSA_ALG_RSA_PSS uses the same hash throughout the algorithm.)
279 the specified hash algorithm.
368 * In the PSA API, the policy for a MAC or AEAD algorithm can specify a
469 * In PSA, allow using a key declared with a base key agreement algorithm
471 agreement algorithm in use matches the algorithm the key was declared with.
510 algorithm parameters (only the size) when comparing the signature in the
512 NULL algorithm parameters entry would look identical to an array of REAL
[all …]
DREADME.md222 * The interface to algorithms is generic, favoring algorithm agility.
/openthread-3.6.0/third_party/mbedtls/repo/tests/data_files/
DMakefile816 …$(OPENSSL) genpkey -algorithm EC -pkeyopt ec_paramgen_curve:prime192v1 -pkeyopt ec_param_enc:named…