| /linux/fs/verity/ |
| H A D | hash_algs.c | 13 .name = "sha256", 78 sha256_init(&ctx.sha256); in fsverity_prepare_hash_state() 79 sha256_update(&ctx.sha256, padded_salt, padded_salt_size); in fsverity_prepare_hash_state() 80 res = kmemdup(&ctx.sha256, sizeof(ctx.sha256), GFP_KERNEL); in fsverity_prepare_hash_state() 116 ctx.sha256 = params->hashstate->sha256; in fsverity_hash_block() 117 sha256_update(&ctx.sha256, data, params->block_size); in fsverity_hash_block() 118 sha256_final(&ctx.sha256, out); in fsverity_hash_block() 142 sha256(data, size, out); in fsverity_hash_buffer()
|
| /linux/lib/crypto/ |
| H A D | Makefile | 214 libsha256-y := sha256.o 219 libsha256-y += arm/sha256-ce.o arm/sha256-core.o 220 $(obj)/arm/sha256-core.S: $(src)/arm/sha256-armv4.pl 222 AFLAGS_arm/sha256-core.o += $(aflags-thumb2-y) 226 libsha256-y += arm64/sha256-core.o 227 $(obj)/arm64/sha256-core.S: $(src)/arm64/sha2-armv8.pl 229 libsha256-$(CONFIG_KERNEL_MODE_NEON) += arm64/sha256-ce.o 232 libsha256-$(CONFIG_PPC) += powerpc/sha256-spe-asm.o 233 libsha256-$(CONFIG_RISCV) += riscv/sha256-riscv64-zvknha_or_zvknhb-zvkb.o 235 libsha256-$(CONFIG_X86) += x86/sha256-ssse3-asm.o \ [all …]
|
| H A D | sha256.c | 3 * SHA-224, SHA-256, HMAC-SHA224, and HMAC-SHA256 library functions 159 #include "sha256.h" /* $(SRCARCH)/sha256.h */ 261 void sha256(const u8 *data, size_t len, u8 out[SHA256_DIGEST_SIZE]) in sha256() function 269 EXPORT_SYMBOL(sha256); 341 sha256(raw_key, raw_key_len, derived_key.b); in __hmac_sha256_preparekey() 496 MODULE_DESCRIPTION("SHA-224, SHA-256, HMAC-SHA224, and HMAC-SHA256 library functions");
|
| /linux/crypto/ |
| H A D | sha256.c | 3 * Crypto API support for SHA-224, SHA-256, HMAC-SHA224, and HMAC-SHA256 158 sha256(data, len, out); in crypto_sha256_digest() 249 /* HMAC-SHA256 */ 338 .base.cra_name = "sha256", 339 .base.cra_driver_name = "sha256-lib", 376 .base.cra_name = "hmac(sha256)", 377 .base.cra_driver_name = "hmac-sha256-lib", 410 MODULE_DESCRIPTION("Crypto API support for SHA-224, SHA-256, HMAC-SHA224, and HMAC-SHA256"); 414 MODULE_ALIAS_CRYPTO("sha256"); 415 MODULE_ALIAS_CRYPTO("sha256-lib"); [all …]
|
| /linux/include/crypto/ |
| H A D | sha2.h | 135 * HMAC key and message context structs, shared by HMAC-SHA224 and HMAC-SHA256. 335 * If you don't need incremental computation, consider sha256() instead. 369 * sha256() - Compute SHA-256 message digest in one shot 376 void sha256(const u8 *data, size_t len, u8 out[SHA256_DIGEST_SIZE]); 407 * struct hmac_sha256_key - Prepared key for HMAC-SHA256 415 * struct hmac_sha256_ctx - Context for computing HMAC-SHA256 of a message 423 * hmac_sha256_preparekey() - Prepare a key for HMAC-SHA256 425 * @raw_key: the raw HMAC-SHA256 key 437 * hmac_sha256_init() - Initialize an HMAC-SHA256 context for a new message 452 * hmac_sha256_init_usingrawkey() - Initialize an HMAC-SHA256 context for a new [all …]
|
| /linux/net/mptcp/ |
| H A D | crypto.c | 35 sha256((__force u8 *)&input, sizeof(input), (u8 *)mptcp_hashed_key); in mptcp_crypto_key_sha()
|
| /linux/include/linux/ |
| H A D | efi_embedded_fw.h | 28 * @sha256: SHA256 of the firmware 34 u8 sha256[32]; member
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-crypt.rst | 25 aes-cbc-essiv:sha256 40 capi:cbc(aes)-essiv:sha256 46 capi:authenc(hmac(sha256),xts(aes))-random 199 …dmsetup create crypt1 --table "0 `blockdev --getsz $1` crypt aes-cbc-essiv:sha256 babebabebabebabe… 205 …dmsetup create crypt2 --table "0 `blockdev --getsize $1` crypt aes-cbc-essiv:sha256 :32:logon:my_p…
|
| H A D | dm-ima.rst | 159 …10 a8c5ff755561c7a28146389d1514c318592af49a ima-buf sha256:4d73481ecce5eadba8ab084640d85bb9ca899af… 200 …10 56c00cc062ffc24ccd9ac2d67d194af3282b934e ima-buf sha256:e7d12c03b958b4e0e53e7363a06376be88d98a1… 204 …active_table_hash=sha256:4d73481ecce5eadba8ab084640d85bb9ca899af4d0a122989252a76efadc5b72;current_… 208 When a device is removed, the device information and a sha256 hash of the 238 …10 790e830a3a7a31590824ac0642b3b31c2d0e8b38 ima-buf sha256:ab9f3c959367a8f5d4403d6ce9c3627dadfa8f9… 243 active_table_hash=sha256:4a7e62efaebfc86af755831998b7db6f59b60d23c9534fb16a4455907957953a, 244 …inactive_table_hash=sha256:9d79c175bc2302d55a183e8f50ad4bafd60f7692fd6249e5fd213e2464384b86,remove… 249 When an inactive table is cleared from the device, the device information and a sha256 hash of the 272 …10 77d347408f557f68f0041acb0072946bb2367fe5 ima-buf sha256:42f9ca22163fdfa548e6229dece2959bc5ce295… 276 …inactive_table_hash=sha256:75c0dc347063bf474d28a9907037eba060bfe39d8847fc0646d75e149045d545;curren… [all …]
|
| /linux/arch/s390/purgatory/ |
| H A D | Makefile | 3 purgatory-y := head.o purgatory.o string.o sha256.o mem.o 8 $(obj)/sha256.o: $(srctree)/lib/crypto/sha256.c FORCE
|
| /linux/arch/mips/include/asm/octeon/ |
| H A D | crypto.h | 8 * MD5/SHA1/SHA256/SHA512 instruction definitions added by 25 * Macros needed to implement MD5/SHA1/SHA256: 29 * The index can be 0-1 (MD5) or 0-2 (SHA1), 0-3 (SHA256). 40 * The index can be 0-1 (MD5) or 0-2 (SHA1), 0-3 (SHA256).
|
| /linux/arch/x86/purgatory/ |
| H A D | Makefile | 3 purgatory-y := purgatory.o stack.o setup-x86_$(BITS).o sha256.o entry64.o string.o 11 $(obj)/sha256.o: $(srctree)/lib/crypto/sha256.c FORCE
|
| /linux/security/apparmor/ |
| H A D | Kconfig | 60 bool "Enable introspection of sha256 hashes for loaded profiles" 76 This option selects whether sha256 hashing of loaded policy 77 is enabled by default. The generation of sha256 hashes for
|
| H A D | crypto.c | 32 sha256(data, len, hash); in aa_calc_hash() 59 aa_info_message("AppArmor sha256 policy hashing enabled"); in init_profile_hash()
|
| /linux/fs/crypto/ |
| H A D | fname.c | 62 u8 sha256[SHA256_DIGEST_SIZE]; member 67 * the strong hash and thus includes the 'sha256' field. This isn't simply 70 #define FSCRYPT_NOKEY_NAME_MAX offsetofend(struct fscrypt_nokey_name, sha256) 373 offsetof(struct fscrypt_nokey_name, sha256)); in fscrypt_fname_disk_to_usr() 385 sha256(&iname->name[sizeof(nokey_name.bytes)], in fscrypt_fname_disk_to_usr() 387 nokey_name.sha256); in fscrypt_fname_disk_to_usr() 473 (ret > offsetof(struct fscrypt_nokey_name, sha256) && in fscrypt_setup_filename() 527 sha256(&de_name[sizeof(nokey_name->bytes)], in fscrypt_match_name() 529 return !memcmp(digest, nokey_name->sha256, sizeof(digest)); in fscrypt_match_name()
|
| /linux/lib/crypto/tests/ |
| H A D | sha256_kunit.c | 6 #include "sha256-testvecs.h" 9 #define HASH sha256 215 .name = "sha256", 222 MODULE_DESCRIPTION("KUnit tests and benchmark for SHA-256 and HMAC-SHA256");
|
| /linux/arch/riscv/purgatory/ |
| H A D | Makefile | 3 purgatory-y := purgatory.o sha256.o entry.o string.o ctype.o memcpy.o memset.o 32 $(obj)/sha256.o: $(srctree)/lib/crypto/sha256.c FORCE
|
| /linux/Documentation/devicetree/bindings/crypto/ |
| H A D | nvidia,tegra234-se-hash.yaml | 11 SHA1, SHA224, SHA256, SHA384, SHA512, SHA3-224, SHA3-256, SHA3-384, SHA3-512 12 HMAC(SHA224), HMAC(SHA256), HMAC(SHA384), HMAC(SHA512)
|
| /linux/lib/crypto/sparc/ |
| H A D | sha256.h | 3 * SHA-256 accelerated using the sparc64 sha256 opcodes 42 pr_info("Using sparc64 sha256 opcode optimized SHA-256/SHA-224 implementation\n"); in sha256_mod_init_arch()
|
| H A D | sha256_asm.S | 30 SHA256 70 SHA256
|
| /linux/drivers/md/ |
| H A D | dm-ima.h | 18 #define DM_IMA_TABLE_HASH_ALG "sha256" 42 * Contains the sha256 hashes of the IMA measurements of the target
|
| /linux/drivers/crypto/ccree/ |
| H A D | cc_hash.h | 87 * @mode: The Hash mode. Supported modes: MD5/SHA1/SHA224/SHA256/SHA384/SHA512 99 * @mode: The Hash mode. Supported modes: MD5/SHA1/SHA224/SHA256/SHA384/SHA512
|
| /linux/lib/crypto/arm64/ |
| H A D | sha2-armv8.pl | 26 # SHA256/512 for ARMv8. 31 # SHA256-hw SHA256(*) SHA512 39 # (*) Software SHA256 results are of lesser relevance, presented 52 # version of SHA256 for 64-bit processors. This is because performance 55 # observed that 32-bit NEON SHA256 performs significantly better than 57 # result 64-bit NEON version of SHA256 was added to provide best 61 # Which is why NEON support is limited to SHA256.] 453 # You'll surely note a lot of similarities with sha256-armv4 module, 454 # and of course it's not a coincidence. sha256-armv4 was used as 775 s/\b(sha256\w+)\s+([qv].*)/unsha256($1,$2)/ge;
|
| /linux/drivers/firmware/efi/ |
| H A D | embedded-firmware.c | 56 sha256(map + i, desc->length, hash); in efi_check_md_for_embedded_firmware() 57 if (memcmp(hash, desc->sha256, 32) == 0) in efi_check_md_for_embedded_firmware()
|
| /linux/samples/tsm-mr/ |
| H A D | tsm_mr_sample.c | 76 { MR_(rtmr0, SHA256) | TSM_MR_F_LIVE }, 81 TSM_MR_(rtmr_crypto_agile, SHA256) | TSM_MR_F_RTMR },
|