| /mbedtls-3.5.0/include/psa/ |
| D | crypto_extra.h | 1192 psa_algorithm_t algorithm);
1967 psa_algorithm_t algorithm; member
1977 return cipher_suite->algorithm; in psa_pake_cs_get_algorithm()
1982 psa_algorithm_t algorithm) in psa_pake_cs_set_algorithm() argument
1984 if (!PSA_ALG_IS_PAKE(algorithm)) { in psa_pake_cs_set_algorithm()
1985 cipher_suite->algorithm = 0; in psa_pake_cs_set_algorithm()
1987 cipher_suite->algorithm = algorithm; in psa_pake_cs_set_algorithm()
|
| D | crypto_se_driver.h | 188 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-3.5.0/tests/suites/ |
| D | test_suite_psa_crypto_entropy.data | 5 # implementation of the algorithm that uses randomization, whether it's
6 # because the algorithm is randomized or because our implementation uses
|
| D | test_suite_psa_crypto_se_driver_hal_mocks.function | 565 psa_algorithm_t algorithm = PSA_ALG_ECDSA(PSA_ALG_SHA_256);
591 psa_set_key_algorithm(&attributes, algorithm);
598 TEST_ASSERT(psa_sign_hash(id, algorithm,
626 psa_algorithm_t algorithm = PSA_ALG_ECDSA(PSA_ALG_SHA_256);
651 psa_set_key_algorithm(&attributes, algorithm);
658 TEST_ASSERT(psa_verify_hash(id, algorithm,
|
| D | test_suite_psa_crypto_storage_format.function | 86 /* Whether the algorithm is implemented as a builtin, i.e. not accelerated,
87 * and calls mbedtls_md() functions that require the hash algorithm to
158 /* Mbed TLS doesn't support certain combinations of key type and algorithm
184 /* Verification only. Verification doesn't use the hash algorithm. */
|
| D | test_suite_psa_crypto_op_fail.misc.data | 6 PSA hash: invalid algorithm
|
| D | test_suite_psa_crypto_generate_key.function | 21 // key lifetime, usage flags, algorithm are irrelevant for this test
|
| D | test_suite_psa_crypto_metadata.function | 14 /* Flags for algorithm classification macros. There is a flag for every
15 * algorithm classification macro PSA_ALG_IS_xxx except for the
326 /* Check that calling PSA_ALG_TRUNCATED_MAC on an algorithm
357 /* 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
|
| D | test_suite_psa_crypto.data | 682 PSA key policy: MAC, wrong algorithm
738 PSA key policy: HMAC, sign-verify, min-length policy, unmatched base alg (different algorithm)
742 PSA key policy: HMAC, sign-verify, min-length policy used as algorithm
762 PSA key policy: cipher, wrong algorithm
786 PSA key policy: AEAD, wrong algorithm
846 PSA key policy: AEAD, min-length policy used as algorithm
866 PSA key policy: asymmetric encryption, wrong algorithm (v1.5/OAEP)
870 PSA key policy: asymmetric encryption, wrong algorithm (OAEP with different hash)
946 PSA key policy: asymmetric signature, wrong hash algorithm
994 PSA key policy: msg asymmetric signature, wrong hash algorithm
[all …]
|
| D | test_suite_pem.data | 30 PEM read (unknown encryption algorithm)
|
| D | test_suite_psa_crypto_slot_management.data | 189 Copy persistent to persistent with enrollment algorithm
|
| /mbedtls-3.5.0/docs/architecture/psa-migration/ |
| D | md-cipher-dispatch.md | 164 * How to decide whether a specific algorithm or key type is supported (eventually based on `MBEDTLS…
171 * Some parameter indicating which algorithm to use.
186 …which hash algorithm to use based on a parameter of type `mbedtls_md_type_t`. (More generally, all…
210 …` is not enabled, but xxx is enabled through PSA, then a request to use algorithm xxx through some…
213 …algorithm is available through the legacy domain, only through the PSA domain. What does this mean…
225 * A legacy hash interface is available and the hash algorithm is implemented in software.
226 * PSA crypto is enabled and the hash algorithm is implemented via PSA.
241 … `psa_crypto_init()` has been called, without having to inspect the specifics of algorithm support.
248 Requirements: given a hash algorithm,
301 …tls_md_info_t *` because this arises when you try to use an unsupported algorithm (`mbedtls_md_inf…
[all …]
|
| D | psa-limitations.md | 88 the hash algorithm potentially used to hash the message being signed:
89 - a hash algorithm used for the encoding function
91 - most commonly MGF1, which in turn is parametrized by a hash algorithm
127 - algorithm specification:
133 - salt length: either <= hashlen (see note), or any depending on algorithm
157 - encoding hash = message hashing algorithm (may differ from MGF1 hash)
182 algorithm identifiers (for SHA-256, SHA-384 and SHA-512), depending of what
188 - the length of the salt MUST be equal to the length of the digest algorithm
|
| D | strategy.md | 110 algorithm-agnostic APIs for a class of algorithms:
245 management (getting a size for a given algorithm, etc.)
246 3. Adapt compile-time guards used to query availability of a given algorithm;
330 particular algorithm is supported: using `MBEDTLS_xxx` macros, and using
338 if it is, the code want the algorithm available in PSA, otherwise, it wants it
474 It should be easy to provide the user with a bunch of `#define`s for algorithm
|
| /mbedtls-3.5.0/library/ |
| D | psa_crypto_invasive.h | 78 psa_algorithm_t algorithm,
|
| D | ssl_tls13_generic.c | 170 uint16_t algorithm; in ssl_tls13_parse_certificate_verify() local
190 algorithm = MBEDTLS_GET_UINT16_BE(p, 0); in ssl_tls13_parse_certificate_verify()
207 if (!mbedtls_ssl_sig_alg_is_offered(ssl, algorithm)) { in ssl_tls13_parse_certificate_verify()
211 (unsigned int) algorithm)); in ssl_tls13_parse_certificate_verify()
216 algorithm, &sig_alg, &md_alg) != 0) { in ssl_tls13_parse_certificate_verify()
226 (unsigned int) algorithm)); in ssl_tls13_parse_certificate_verify()
|
| D | psa_crypto_pake.c | 229 operation->alg = cipher_suite.algorithm; in mbedtls_psa_pake_setup()
232 if (cipher_suite.algorithm == PSA_ALG_JPAKE) { in mbedtls_psa_pake_setup()
|
| /mbedtls-3.5.0/docs/proposed/ |
| D | psa-conditional-inclusion-c.md | 101 …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…
|
| D | psa-driver-interface.md | 22 … is available for a particular combination of parameters (cryptographic algorithm, key type and si…
93 …orithms"` (optional, list of strings). Each element is an [algorithm specification](#algorithm-spe…
106 * If the mechanism involves an algorithm:
108 …`"algorithms"` property includes an [algorithm specification](#algorithm-specifications) that matc…
114 …property includes a [key type specification](#key-type-specifications) that matches this algorithm.
119 …algorithm, key type and key size, and all the capabilities map the entry point to the same functio…
121 …rs have applicable capabilities for a given combination of entry point, algorithm, key type and ke…
127 …nistic ECDSA signatures (but not signature verification) using any hash algorithm and any curve th…
150 …algorithm specification is a string consisting of a `PSA_ALG_xxx` macro that specifies a cryptogra…
164 An algorithm specification is a string consisting of a `PSA_KEY_TYPE_xxx` macro that specifies a ke…
[all …]
|
| D | psa-driver-developer-guide.md | 20 … is available for a particular combination of parameters (cryptographic algorithm, key type and si…
|
| /mbedtls-3.5.0/docs/architecture/ |
| D | mbed-crypto-storage-specification.md | 57 * policy usage algorithm (4 bytes): `psa_algorithm_t` value
207 * policy usage algorithm (4 bytes): `psa_algorithm_t` value
208 * policy enrollment algorithm (4 bytes): `psa_algorithm_t` value [NEW:1.1.0]
267 * policy usage algorithm (4 bytes): `psa_algorithm_t` value.
268 * policy enrollment algorithm (4 bytes): `psa_algorithm_t` value.
327 * policy usage algorithm (4 bytes): `psa_algorithm_t` value.
328 * policy enrollment algorithm (4 bytes): `psa_algorithm_t` value.
418 * policy usage algorithm (4 bytes): `psa_algorithm_t` value.
419 * policy enrollment algorithm (4 bytes): `psa_algorithm_t` value.
|
| /mbedtls-3.5.0/ |
| D | BRANCHES.md | 39 cryptographic algorithm does not break code that does not use that
40 algorithm).
|
| D | ChangeLog | 27 - Only a single digest algorithm per message is supported.
128 * The key derivation algorithm PSA_ALG_TLS12_ECJPAKE_TO_PMS cannot be
249 Only the ECC primitive with secp256r1 curve and SHA-256 hash algorithm
314 using PSA_ALG_TLS12_ECJPAKE_TO_PMS as the key derivation algorithm.
396 first algorithm would not get sent and an entry consisting of two random
494 * Extend the existing PSA_ALG_TLS12_PSK_TO_MS() algorithm to support
675 * Return PSA_ERROR_INVALID_ARGUMENT if the algorithm passed to one-shot
676 AEAD functions is not an AEAD algorithm. This aligns them with the
812 This algorithm now accepts only the same salt length for verification
813 that it produces when signing, as documented. Use the new algorithm
[all …]
|
| /mbedtls-3.5.0/programs/ |
| D | README.md | 38 …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-3.5.0/docs/ |
| D | 3.0-migration-guide.md | 229 `MBEDTLS_SHA512_NO_SHA384` and you need the SHA-384 algorithm, then add
452 the hash algorithm used when signing a hash. (The requirements when signing
612 ### Strengthen default algorithm selection for X.509
614 …cribed in the section [Strengthen default algorithm selection for X.509 and TLS](#strengthen-defau…
1012 ### Strengthen default algorithm selection for X.509 and TLS
|
