| /lib/mbedtls/ |
| A D | Kconfig | 39 This option enables support of hashing using SHA1 algorithm 46 This option enables support of hashing using SHA256 algorithm 54 This option enables support of hashing using SHA512 algorithm 62 This option enables support of hashing using SHA384 algorithm 69 This option enables support of hashing using MD5 algorithm 100 key crypto algorithm. 170 This option enables support of hashing using SHA1 algorithm 224 This option enables support of hashing using MD5 algorithm 261 key crypto algorithm. 408 key crypto algorithm in SPL. [all …]
|
| /lib/libavb/ |
| A D | avb_vbmeta_image.c | 21 const AvbAlgorithmData* algorithm; in avb_vbmeta_image_verify() local 137 algorithm = avb_get_algorithm_data(h.algorithm_type); in avb_vbmeta_image_verify() 138 if (!algorithm) { in avb_vbmeta_image_verify() 144 if (h.hash_size != algorithm->hash_len) { in avb_vbmeta_image_verify() 200 algorithm->padding, in avb_vbmeta_image_verify() 201 algorithm->padding_len); in avb_vbmeta_image_verify()
|
| A D | avb_crypto.c | 338 const AvbAlgorithmData* avb_get_algorithm_data(AvbAlgorithmType algorithm) { in avb_get_algorithm_data() argument 339 if ((size_t)algorithm < _AVB_ALGORITHM_NUM_TYPES) { in avb_get_algorithm_data() 340 return &algorithm_data[algorithm]; in avb_get_algorithm_data()
|
| A D | avb_crypto.h | 106 const AvbAlgorithmData* avb_get_algorithm_data(AvbAlgorithmType algorithm)
|
| /lib/mbedtls/external/mbedtls/include/psa/ |
| A D | crypto_extra.h | 942 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 D | crypto_se_driver.h | 176 psa_algorithm_t algorithm); 382 psa_algorithm_t algorithm, 481 psa_algorithm_t algorithm, 726 psa_algorithm_t algorithm, 768 psa_algorithm_t algorithm,
|
| /lib/ |
| A D | Kconfig | 34 Enables software based BCH ECC algorithm present in lib/bch.c 466 bool "Support the AES algorithm" 571 The SHA1 algorithm produces a 160-bit (20-byte) hash value 616 The CRC32 algorithm produces 32-bit checksum value. For FIT 627 The SHA1 algorithm produces a 160-bit (20-byte) hash value 686 The SHA1 algorithm produces a 160-bit (20-byte) hash value 720 bool "Support MD5 algorithm" 729 bool "Support MD5 algorithm in SPL" 829 This enables support for the LZO compression algorithm. 836 This enables support for GZIP compression algorithm. [all …]
|
| /lib/crypto/ |
| A D | Kconfig | 22 bool "Asymmetric public-key crypto algorithm subtype" 27 ENOPKG will be reported if the requisite algorithm is unavailable. 30 bool "Asymmetric public-key crypto algorithm subtype within SPL" 36 ENOPKG will be reported if the requisite algorithm is unavailable.
|
| A D | x509.asn1 | 24 algorithm OBJECT IDENTIFIER ({ x509_note_OID }), 48 algorithm AlgorithmIdentifier,
|
| A D | pkcs7.asn1 | 36 algorithm OBJECT IDENTIFIER ({ pkcs7_note_OID }), 119 algorithm OBJECT IDENTIFIER ({ pkcs7_note_OID }),
|
| A D | mscode.asn1 | 26 algorithm OBJECT IDENTIFIER ({ mscode_note_digest_algo }),
|
| /lib/crypt/ |
| A D | Kconfig | 16 Enables support for the sha256crypt password-hashing algorithm. 23 Enables support for the sha512crypt password-hashing algorithm.
|
| /lib/mbedtls/external/mbedtls/docs/architecture/psa-migration/ |
| A D | psa-legacy-bridges.md | 92 …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_… 251 …algorithm. “Same key material” is straightforward, but “same algorithm” is not, because a PK conte… 256 …algorithm, 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 D | psa-limitations.md | 96 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 D | md-cipher-dispatch.md | 220 * 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… 269 …algorithm 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 …]
|
| /lib/ecdsa/ |
| A D | Kconfig | 5 This enables the ECDSA (elliptic curve signature) algorithm for FIT 6 image verification in U-Boot. The ECDSA algorithm is implemented
|
| /lib/mbedtls/external/mbedtls/docs/ |
| A D | driver-only-builds.md | 34 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 D | psa-transition.md | 278 The algorithm encodes the mode and if relevant the padding type: 300 …algorithm value `PSA_ALG_yyy`, the symbol `PSA_WANT_ALG_yyy` is defined with a non-zero value if t… 426 …algorithm 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 …]
|
| /lib/rsa/ |
| A D | Kconfig | 7 RSA support. This enables the RSA algorithm used for FIT image 10 The Modular Exponentiation algorithm in RSA is implemented using 75 algorithm used in FIT image verification. It required RSA Key as
|
| /lib/mbedtls/external/mbedtls/tests/suites/ |
| A 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
|
| A 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,
|
| A D | test_suite_psa_crypto_op_fail.misc.data | 6 PSA hash: invalid algorithm
|
| A D | test_suite_psa_crypto_generate_key.function | 21 // key lifetime, usage flags, algorithm are irrelevant for this test
|
| /lib/mbedtls/external/mbedtls/library/ |
| A D | psa_crypto_invasive.h | 73 psa_algorithm_t algorithm,
|
| A D | ssl_tls13_generic.c | 221 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()
|