Home
last modified time | relevance | path

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

12

/mbedtls-development/include/psa/
A Dcrypto_extra.h1190 psa_algorithm_t algorithm
1747 psa_algorithm_t algorithm; member
1757 return(cipher_suite->algorithm); in psa_pake_cs_get_algorithm()
1762 psa_algorithm_t algorithm) in psa_pake_cs_set_algorithm() argument
1764 if(!PSA_ALG_IS_PAKE(algorithm)) in psa_pake_cs_set_algorithm()
1765 cipher_suite->algorithm = 0; in psa_pake_cs_set_algorithm()
1767 cipher_suite->algorithm = algorithm; in psa_pake_cs_set_algorithm()
A Dcrypto_se_driver.h188 psa_algorithm_t algorithm);
394 psa_algorithm_t algorithm,
493 psa_algorithm_t algorithm,
738 psa_algorithm_t algorithm,
780 psa_algorithm_t algorithm,
/mbedtls-development/ChangeLog.d/
A Dpsa_alg_rsa_pss.txt3 This algorithm now accepts only the same salt length for verification
4 that it produces when signing, as documented. Use the new algorithm
A Dpsa_crypto_api_macros.txt7 for algorithm values that fully encode the hashing step, as per the PSA
/mbedtls-development/library/
A Dssl_tls13_generic.c315 uint16_t algorithm; in ssl_tls13_parse_certificate_verify() local
329 algorithm = MBEDTLS_GET_UINT16_BE( p, 0 ); in ssl_tls13_parse_certificate_verify()
346 if( ! ssl_tls13_sig_alg_is_offered( ssl, algorithm ) ) in ssl_tls13_parse_certificate_verify()
351 ( unsigned int ) algorithm ) ); in ssl_tls13_parse_certificate_verify()
356 switch( algorithm ) in ssl_tls13_parse_certificate_verify()
376 ( unsigned int ) algorithm ) ); in ssl_tls13_parse_certificate_verify()
A Dpsa_crypto_invasive.h78 psa_algorithm_t algorithm,
A Dpsa_crypto.c499 psa_algorithm_t algorithm, in psa_mac_key_can_do() argument
502 if( PSA_ALG_IS_HMAC( algorithm ) ) in psa_mac_key_can_do()
508 if( PSA_ALG_IS_BLOCK_CIPHER_MAC( algorithm ) ) in psa_mac_key_can_do()
/mbedtls-development/tests/suites/
A 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
A 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,
A Dtest_suite_psa_crypto_generate_key.function21 // key lifetiem, usage flags, algorithm are irrelevant for this test
A Dtest_suite_psa_crypto.data679 PSA key policy: MAC, wrong algorithm
1601 PSA MAC setup: bad algorithm (unsupported HMAC hash algorithm)
1605 PSA MAC setup: bad algorithm (not a MAC algorithm)
1852 PSA cipher setup: bad algorithm (unknown cipher algorithm)
1856 PSA cipher setup: bad algorithm (not a cipher algorithm)
1898 PSA cipher encrypt: bad algorithm (unknown cipher algorithm)
1902 PSA cipher encrypt: bad algorithm (not a cipher algorithm)
2047 PSA cipher decrypt: bad algorithm (unknown cipher algorithm)
2050 PSA cipher decrypt: bad algorithm (not a cipher algorithm)
4082 PSA encrypt: invalid algorithm
[all …]
A 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
323 /* Check that calling PSA_ALG_TRUNCATED_MAC on an algorithm
355 /* Check that calling PSA_ALG_AT_LEAST_THIS_LENGTH_MAC on an algorithm
451 /* Check that calling PSA_ALG_AEAD_WITH_SHORTENED_TAG on an algorithm
485 * algorithm earlier constructed with PSA_ALG_AEAD_WITH_SHORTENED_TAG
A Dtest_suite_pem.data25 PEM read (unknown encryption algorithm)
A Dtest_suite_psa_crypto_slot_management.data189 Copy persistent to persistent with enrollment algorithm
A 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. */
A Dtest_suite_x509parse.data1428 X509 CRT ASN1 (TBS, inv SubPubKeyInfo, inv algorithm tag)
1432 X509 CRT ASN1 (TBS, inv SubPubKeyInfo, algorithm length missing)
1436 X509 CRT ASN1 (TBS, inv SubPubKeyInfo, algorithm inv length encoding)
1440 X509 CRT ASN1 (TBS, inv SubPubKeyInfo, algorithm length out of bounds)
1444 X509 CRT ASN1 (TBS, inv SubPubKeyInfo, algorithm empty)
1448 X509 CRT ASN1 (TBS, inv SubPubKeyInfo, algorithm unknown)
A Dtest_suite_x509parse.function635 TEST_ASSERT( "Unknown algorithm profile" == 0 );
/mbedtls-development/docs/architecture/
A 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.
/mbedtls-development/docs/
A 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 …]
A D3.0-migration-guide.md208 `MBEDTLS_SHA512_NO_SHA384` and you need the SHA-384 algorithm, then add
424 the hash algorithm used when signing a hash. (The requirements when signing
584 ### Strengthen default algorithm selection for X.509
586 …cribed in the section [Strengthen default algorithm selection for X.509 and TLS](#strengthen-defau…
984 ### Strengthen default algorithm selection for X.509 and TLS
/mbedtls-development/docs/proposed/
A 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…
A Dpsa-driver-interface.md89 …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…
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…
428 A driver may declare an `"init"` entry point in a capability with no algorithm, key type or key siz…
497 Random generation is not parametrized by an algorithm. The choice of algorithm is up to the driver.
[all …]
A Dpsa-driver-developer-guide.md20 … is available for a particular combination of parameters (cryptographic algorithm, key type and si…
/mbedtls-development/programs/
A 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.
/mbedtls-development/
A DChangeLog71 This separates config option enabling the SHA384 algorithm from option
72 enabling the SHA512 algorithm. Fixes #4034.
74 This separates config option enabling the SHA224 algorithm from option
143 specified hash algorithm.
396 that PSA_ALG_RSA_PSS uses the same hash throughout the algorithm.)
512 * In the PSA API, the policy for a MAC or AEAD algorithm can specify a
615 agreement algorithm in use matches the algorithm the key was declared with.
1141 unsupported algorithm. Fixes ARMmbed/mbed-crypto#254.
2441 * Fix insufficient support for signature-hash-algorithm extension,
4020 * Added blowfish algorithm (Generic and cipher layer)
[all …]

Completed in 73 milliseconds

12