Home
last modified time | relevance | path

Searched refs:SHA384 (Results 1 – 10 of 10) sorted by relevance

/openbmc/qemu/tests/bench/
H A Dbenchmark-crypto-hash.c95 TEST_ONE(SHA384, 512); in main()
96 TEST_ONE(SHA384, 1024); in main()
97 TEST_ONE(SHA384, 4096); in main()
98 TEST_ONE(SHA384, 16384); in main()
/openbmc/bmcweb/redfish-core/include/generated/enums/
H A Dkey_policy.hpp23 SHA384, enumerator
63 {NVMeoFSecureHashType::SHA384, "SHA384"},
H A Dkey.hpp48 SHA384, enumerator
92 {NVMeoFSecureHashType::SHA384, "SHA384"},
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-security/trusted-services/corstone1000/psa-apitest/
H A D0003-corstone1000-Disable-SHA512-384.patch6 SHA512 and SHA384 is not available on Cryptocell (hardware accelerator)
/openbmc/u-boot/lib/
H A DKconfig264 config SHA384 config
265 bool "Enable SHA384 support"
268 This option enables support of hashing using SHA384 algorithm.
270 The SHA384 algorithm produces a 384-bit (48-byte) hash value
/openbmc/u-boot/
H A DKconfig289 bool "Support SHA384 checksum of FIT image contents"
291 select SHA384
293 Enable this to support SHA384 checksum of FIT image contents. A
294 SHA384 checksum is a 384-bit (48-byte) hash value used to check that
/openbmc/u-boot/common/spl/
H A DKconfig287 consider SHA256 or SHA384.
299 attacks. For more security, consider SHA256 or SHA384.
311 bool "Support SHA384"
313 select SHA384
316 Enable this to support SHA384 in FIT images within SPL. A SHA384
/openbmc/linux/drivers/crypto/
H A DKconfig410 Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512
413 SHA1/SHA224/SHA256/SHA384/SHA512 algorithms.
725 SHA384 and SHA512 hash algorithms for both basic hash and HMAC.
/openbmc/linux/Documentation/crypto/
H A Dapi-intro.rst194 - Jean-Luc Cooke (SHA256, SHA384, SHA512)
/openbmc/u-boot/cmd/
H A DKconfig612 depends on SHA256 && SHA384 && SHA512