/openbmc/qemu/tests/bench/ |
H A D | benchmark-crypto-hash.c | 100 TEST_ONE(SHA256, 512); in main() 101 TEST_ONE(SHA256, 1024); in main() 102 TEST_ONE(SHA256, 4096); in main() 103 TEST_ONE(SHA256, 16384); in main()
|
/openbmc/bmcweb/redfish-core/include/generated/enums/ |
H A D | key_policy.hpp | 24 SHA256, enumerator 64 {NVMeoFSecureHashType::SHA256, "SHA256"},
|
H A D | key.hpp | 49 SHA256, enumerator 93 {NVMeoFSecureHashType::SHA256, "SHA256"},
|
/openbmc/u-boot/drivers/crypto/fsl/ |
H A D | fsl_hash.c | 29 SHA256 enumerator 50 return SHA256; in get_hash_type() 204 if (caam_hash(pbuf, buf_len, pout, SHA256)) in hw_sha256()
|
/openbmc/linux/arch/sparc/crypto/ |
H A D | sha256_asm.S | 31 SHA256 71 SHA256
|
H A D | opcodes.h | 25 #define SHA256 \ macro
|
/openbmc/linux/drivers/crypto/ |
H A D | Kconfig | 42 tristate "PadLock driver for SHA1 and SHA256 algorithms" 48 Use VIA PadLock for SHA1/SHA256 algorithms. 347 Select this to offload Exynos from HASH MD5/SHA1/SHA256. 348 This will select software SHA1, MD5 and SHA256 as they are 410 Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512 413 SHA1/SHA224/SHA256/SHA384/SHA512 algorithms. 472 The Freescale i.MX23/i.MX28 has SHA1/SHA256 and AES128 CBC/ECB 549 - SHA256, HMAC-SHA256 566 - SHA256, HMAC-SHA256 629 hardware hash accelerator. Supporting MD5/SHA1/SHA224/SHA256 [all …]
|
/openbmc/bmcweb/scripts/ |
H A D | generate_auth_certificates.py | 104 private_key=private_key, algorithm=hashes.SHA256() 111 csr.sign(ca_key, algorithm=hashes.SHA256()) 164 signed = builder.sign(private_key=ca_key, algorithm=hashes.SHA256()) 220 signed = builder.sign(private_key=ca_key, algorithm=hashes.SHA256())
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/nss/nss/ |
H A D | system-pkcs11.txt | 4 …ECC,RSA,DSA,DH,RC2,RC4,DES,RANDOM,SHA1,MD5,MD2,SSL,TLS,AES,Camellia,SEED,SHA256,SHA512] askpw=any …
|
/openbmc/openbmc/poky/meta/recipes-support/libgcrypt/files/ |
H A D | no-bench-slope.patch | 21 { "hashtest-6g", "hashtest", "--hugeblock --gigs 6 SHA1 SHA256 SHA512 "
|
/openbmc/linux/Documentation/devicetree/bindings/crypto/ |
H A D | img-hash.txt | 4 SHA1, SHA224, SHA256 and MD5 hashes
|
/openbmc/linux/Documentation/crypto/ |
H A D | architecture.rst | 377 For example, HMAC(SHA256) is implemented with hmac.c and 407 SHA256 is instantiated. The cipher handle for the SHA256 instance is 410 At one time, the HMAC implementation requires a SHA256 operation 411 where the SHA256 cipher handle is used. 413 2. The HMAC instance now invokes the SHASH API with the SHA256 cipher
|
H A D | api-intro.rst | 194 - Jean-Luc Cooke (SHA256, SHA384, SHA512) 220 SHA256/384/512 algorithm contributors:
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/cli11/cli11/ |
H A D | 0001-Do-not-download-the-catch-framework-during-configure.patch | 30 - EXPECTED_HASH SHA256=ea379c4a3cb5799027b1eb451163dff065a3d641aaba23bf4e24ee6b536bd9bc)
|
/openbmc/openbmc/meta-phosphor/recipes-phosphor/flash/ |
H A D | phosphor-image-signing.bb | 37 echo HashType=RSA-SHA256 > "${UNPACKDIR}/hashfunc"
|
/openbmc/u-boot/lib/ |
H A D | Kconfig | 242 config SHA256 config 243 bool "Enable SHA256 support" 245 This option enables support of hashing using SHA256 algorithm. 247 The SHA256 algorithm produces a 256-bit (32-byte) hash value
|
/openbmc/openbmc/poky/meta/recipes-extended/shadow/files/ |
H A D | login.defs_shadow-sysroot | 304 # If set to SHA256, SHA256-based algorithm will be used for encrypting password 315 # Only works if ENCRYPT_METHOD is set to SHA256 or SHA512.
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/minifi-cpp/files/ |
H A D | 0002-Fix-osspuuid-build.patch | 50 - URL_HASH "SHA256=11a615225baa5f8bb686824423f50e4427acd3f70d394765bdff32801f0fd5b0"
|
/openbmc/u-boot/ |
H A D | Kconfig | 280 bool "Support SHA256 checksum of FIT image contents" 282 select SHA256 284 Enable this to support SHA256 checksum of FIT image contents. A 285 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
|
/openbmc/openbmc/poky/documentation/migration-guides/ |
H A D | migration-3.1.rst | 159 Previously, recipes by tradition included both SHA256 and MD5 checksums 163 the SHA256 sum will now be printed. The md5sum will still be verified if
|
/openbmc/u-boot/common/spl/ |
H A D | Kconfig | 275 should consider SHA1 or SHA256. 287 consider SHA256 or SHA384. 299 attacks. For more security, consider SHA256 or SHA384. 302 bool "Support SHA256" 304 select SHA256 306 Enable this to support SHA256 in FIT images within SPL. A SHA256 367 select SHA256 377 select SHA256
|
/openbmc/linux/tools/testing/selftests/sgx/ |
H A D | sigstruct.c | 368 SHA256((unsigned char *)&payload, sizeof(payload), digest); in encl_measure()
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/hostapd/hostapd/ |
H A D | defconfig | 100 # Include support for optional SHA256 cipher suite in EAP-GPSK
|
/openbmc/linux/arch/arm64/boot/dts/xilinx/ |
H A D | zynqmp-sm-k26-revA.dts | 216 label = "SHA256";
|
/openbmc/openbmc/poky/meta/classes/ |
H A D | create-spdx-2.2.bbclass | 175 algorithm="SHA256", 258 …bb.debug(1, "Debug source %s with SHA256 %s not found in any dependency" % (str(debugsrc_path), fi… 339 if checksum.algorithm == "SHA256":
|