Home
last modified time | relevance | path

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

12

/mbedtls/include/psa/
A Dcrypto_extra.h942 psa_algorithm_t algorithm);
1711 psa_algorithm_t algorithm; member
1721 return cipher_suite->algorithm; in psa_pake_cs_get_algorithm()
1726 psa_algorithm_t algorithm) in psa_pake_cs_set_algorithm() argument
1728 if (!PSA_ALG_IS_PAKE(algorithm)) { in psa_pake_cs_set_algorithm()
1729 cipher_suite->algorithm = 0; in psa_pake_cs_set_algorithm()
1731 cipher_suite->algorithm = algorithm; in psa_pake_cs_set_algorithm()
A Dcrypto_se_driver.h176 psa_algorithm_t algorithm);
382 psa_algorithm_t algorithm,
481 psa_algorithm_t algorithm,
726 psa_algorithm_t algorithm,
768 psa_algorithm_t algorithm,
/mbedtls/docs/architecture/psa-migration/
A Dpsa-legacy-bridges.md92 …ontrivial data format. Therefore the only gap is with metadata, namely specifying a hash algorithm.
127 …there is no algorithm that can be used with multiple types, and PSA keys have a policy that (for t…
139 * Simultaneously supporting **a key type and an algorithm**.
143 …_key_type_t` value and an algorithm which is normally encoded as policy information in a `psa_key_…
251algorithm. “Same key material” is straightforward, but “same algorithm” is not, because a PK conte…
256algorithm, which as discussed above cannot be fully deduced from the `mbedtls_pk_context` object. …
283 * `mbedtls_pk_get_psa_attributes` sets the algorithm usage policy based on information in the key o…
284 …* For an RSA key with the `MBEDTLS_RSA_PKCS_V15` padding mode, the algorithm policy is `PSA_ALG_RS…
286 …* For an `MBEDTLS_PK_ECKEY` or `MBEDTLS_PK_ECDSA` with a sign/verify usage, the algorithm policy i…
287 …Y` or `MBEDTLS_PK_ECDKEY_DH` with the usage `PSA_KEY_USAGE_DERIVE`, the algorithm is `PSA_ALG_ECDH…
[all …]
A Dpsa-limitations.md96 the hash algorithm potentially used to hash the message being signed:
97 - a hash algorithm used for the encoding function
99 - most commonly MGF1, which in turn is parametrized by a hash algorithm
135 - algorithm specification:
141 - salt length: either <= hashlen (see note), or any depending on algorithm
165 - encoding hash = message hashing algorithm (may differ from MGF1 hash)
190 algorithm identifiers (for SHA-256, SHA-384 and SHA-512), depending of what
196 - the length of the salt MUST be equal to the length of the digest algorithm
A Dmd-cipher-dispatch.md220 * How to decide whether a specific algorithm or key type is supported (eventually based on `MBEDTLS…
227 * Some parameter indicating which algorithm to use.
242 …which hash algorithm to use based on a parameter of type `mbedtls_md_type_t`. (More generally, all…
269algorithm is available through the legacy domain, only through the PSA domain. What does this mean…
281 * A legacy hash interface is available and the hash algorithm is implemented in software.
282 * PSA crypto is enabled and the hash algorithm is implemented via PSA.
297 … `psa_crypto_init()` has been called, without having to inspect the specifics of algorithm support.
304 Requirements: given a hash algorithm,
419 #### MD algorithm support macros
507 If given an algorithm as an `mbedtls_md_type_t type` (possibly being the `type` field of a `const m…
[all …]
A Dstrategy.md116 algorithm-agnostic APIs for a class of algorithms:
255 management (getting a size for a given algorithm, etc.)
256 3. Adapt compile-time guards used to query availability of a given algorithm;
319 particular algorithm is supported: using `MBEDTLS_xxx` macros, and using
327 if it is, the code want the algorithm available in PSA, otherwise, it wants it
330 As much as possible, we're trying to create for each algorithm a single new
443 It should be easy to provide the user with a bunch of `#define`s for algorithm
/mbedtls/docs/
A Ddriver-only-builds.md34 means the algorithm will be available in the PSA Crypto API.
60 - finite-field Diffie-Hellman: FFDH algorithm, DH key types.
98 a hash algorithm that is provided only by a driver, as mentioned in [General
101 If you want to check at compile-time whether a certain hash algorithm is
116 - Required hash algorithm(s) as explained in [Hashes](#hashes) section.
250 that can be used with this algorithm are also declared as accelerated.
276 The same holds for the associated algorithm:
309 algorithm/mode you can:
317 - Enable desired PSA algorithm(s):
357 - If an algorithm other than CCM and GCM (see
[all …]
A Dpsa-transition.md278 The algorithm encodes the mode and if relevant the padding type:
300algorithm value `PSA_ALG_yyy`, the symbol `PSA_WANT_ALG_yyy` is defined with a non-zero value if t…
426algorithm from RFC 4615 calculated by `mbedtls_aes_cmac_prf_128` at the time of writing. You can i…
485 ### Hash algorithm metadata
509 2. Call `mbedtls_md_setup` to select the hash algorithm, with `hmac=0`. Then call `mbedtls_md_start…
552 2. Call `mbedtls_md_setup` to select the hash algorithm, with `hmac=1`. Then call `mbedtls_md_hmac_…
681 A key's policy indicates what algorithm(s) it can be used with (usage algorithm policy) and what op…
952 Most signature algorithms involve a hash algorithm. See “[Hash mechanism selection](#hash-mechanism…
999 The PSA API has two algorithm constructors:
1044 … hash algorithm is used for MGF1 and to hash the label. The PSA API does not offer a way to choose…
[all …]
/mbedtls/tests/suites/
A Dtest_suite_psa_crypto_se_driver_hal_mocks.function565 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,
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_op_fail.misc.data6 PSA hash: invalid algorithm
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
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
A Dtest_suite_psa_crypto_generate_key.function21 // key lifetime, usage flags, algorithm are irrelevant for this test
A Dtest_suite_psa_crypto.data836 PSA key policy: MAC, wrong algorithm
1754 PSA MAC setup: bad algorithm (unsupported HMAC hash algorithm)
1758 PSA MAC setup: bad algorithm (not a MAC algorithm)
2201 PSA cipher setup: bad algorithm (unknown cipher algorithm)
2205 PSA cipher setup: bad algorithm (not a cipher algorithm)
2247 PSA cipher encrypt: bad algorithm (unknown cipher algorithm)
2251 PSA cipher encrypt: bad algorithm (not a cipher algorithm)
2396 PSA cipher decrypt: bad algorithm (unknown cipher algorithm)
2399 PSA cipher decrypt: bad algorithm (not a cipher algorithm)
5086 PSA encrypt: invalid algorithm
[all …]
A Dtest_suite_psa_crypto_storage_format.function87 /* Mbed TLS doesn't support certain combinations of key type and algorithm
113 /* Verification only. Verification doesn't use the hash algorithm. */
/mbedtls/library/
A Dssl_tls13_generic.c221 uint16_t algorithm; in ssl_tls13_parse_certificate_verify() local
241 algorithm = MBEDTLS_GET_UINT16_BE(p, 0); in ssl_tls13_parse_certificate_verify()
260 if (!mbedtls_ssl_sig_alg_is_offered(ssl, algorithm)) { in ssl_tls13_parse_certificate_verify()
264 (unsigned int) algorithm)); in ssl_tls13_parse_certificate_verify()
269 algorithm, &sig_alg, &md_alg) != 0) { in ssl_tls13_parse_certificate_verify()
279 (unsigned int) algorithm)); in ssl_tls13_parse_certificate_verify()
A Dpsa_crypto_invasive.h73 psa_algorithm_t algorithm,
A Dpsa_crypto_pake.c221 operation->alg = cipher_suite.algorithm; in mbedtls_psa_pake_setup()
224 if (cipher_suite.algorithm == PSA_ALG_JPAKE) { in mbedtls_psa_pake_setup()
/mbedtls/docs/architecture/
A Dpsa-crypto-implementation-structure.md77 Summary of files to modify when adding a new algorithm or key type:
115 Constants (algorithm identifiers, key type identifiers, etc.) and associated destructor macros (e.g…
119 …_xxx`), DH group families (`PSA_DH_FAMILY_xxx`). If Mbed TLS defines an algorithm or a key type th…
146 …ementing a new algorithm or key type, there are typically things to change in `library/crypto.c` (…
159 * Attempt to perform an operation with a combination of key type and algorithm that is not valid or…
162 When adding a new key type or algorithm:
A Dmbed-crypto-storage-specification.md59 * policy usage algorithm (4 bytes): `psa_algorithm_t` value
209 * policy usage algorithm (4 bytes): `psa_algorithm_t` value
210 * policy enrollment algorithm (4 bytes): `psa_algorithm_t` value [NEW:1.1.0]
269 * policy usage algorithm (4 bytes): `psa_algorithm_t` value.
270 * policy enrollment algorithm (4 bytes): `psa_algorithm_t` value.
329 * policy usage algorithm (4 bytes): `psa_algorithm_t` value.
330 * policy enrollment algorithm (4 bytes): `psa_algorithm_t` value.
420 * policy usage algorithm (4 bytes): `psa_algorithm_t` value.
421 * policy enrollment algorithm (4 bytes): `psa_algorithm_t` value.
/mbedtls/docs/proposed/
A Dpsa-conditional-inclusion-c.md110 …A_ALG_xxx`, the symbol **`PSA_WANT_ALG_xxx`** indicates that support for this algorithm is desired.
185 An entry point can be eliminated entirely if no algorithm requires it.
205algorithm, include a capability with that algorithm, the key types that apply to that algorithm, n…
231 …mandate a compile-time error if a key type is required, but no matching algorithm, or vice versa? …
237 This is especially relevant to suppress a mechanism completely if there is no matching algorithm. F…
A Dpsa-driver-interface.md95 …orithms"` (optional, list of strings). Each element is an [algorithm specification](#algorithm-spe…
108 * If the mechanism involves an algorithm:
110 …`"algorithms"` property includes an [algorithm specification](#algorithm-specifications) that matc…
116 …property includes a [key type specification](#key-type-specifications) that matches this algorithm.
152algorithm specification is a string consisting of a `PSA_ALG_xxx` macro that specifies a cryptogra…
320 …cure element implements the `"key_derivation"` family for the specified algorithm, the core calls …
371 * `PSA_KEY_DERIVATION_INPUT_TYPE_INVALID`: the step is invalid for the algorithm of the operation t…
372 * `PSA_KEY_DERIVATION_INPUT_TYPE_OMITTED`: the step is optional for the algorithm of the operation …
425 * `alg` is the algorithm for the key derivation operation. It does not include a key agreement comp…
439 At the time of writing, no standard key derivation algorithm has long inputs. It is likely that suc…
[all …]
/mbedtls/programs/psa/
A Dkey_ladder_demo.sh11 wrap some data using an AEAD algorithm.
/mbedtls/
A DBRANCHES.md45 cryptographic algorithm does not break code that does not use that
46 algorithm).
/mbedtls/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.

Completed in 829 milliseconds

12