Home
last modified time | relevance | path

Searched full:sha256 (Results 1 – 25 of 153) sorted by relevance

1234567

/linux/fs/verity/
H A Dhash_algs.c13 .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/drivers/crypto/
H A Dpadlock-sha.c228 .cra_name = "sha256",
229 .cra_driver_name = "sha256-padlock",
309 .cra_name = "sha256",
310 .cra_driver_name = "sha256-padlock-nano",
330 struct shash_alg *sha256; in padlock_init() local
346 sha256 = &sha256_alg; in padlock_init()
349 sha256 = &sha256_alg_nano; in padlock_init()
356 rc = crypto_register_shash(sha256); in padlock_init()
360 printk(KERN_NOTICE PFX "Using VIA PadLock ACE for SHA1/SHA256 algorithms.\n"); in padlock_init()
368 printk(KERN_ERR PFX "VIA PadLock SHA1/SHA256 initialization failed.\n"); in padlock_init()
[all …]
H A DKconfig42 tristate "PadLock driver for SHA1 and SHA256 algorithms"
48 Use VIA PadLock for SHA1/SHA256 algorithms.
199 protected key HMAC support for SHA224, SHA256, SHA384 and SHA512.
411 Select this to offload Exynos from HASH MD5/SHA1/SHA256.
412 This will select software SHA1, MD5 and SHA256 as they are
474 Some Atmel processors have SHA1/SHA224/SHA256/SHA384/SHA512
477 SHA1/SHA224/SHA256/SHA384/SHA512 algorithms.
536 The Freescale i.MX23/i.MX28 has SHA1/SHA256 and AES128 CBC/ECB
606 - SHA256, HMAC-SHA256
623 - SHA256, HMAC-SHA256
[all …]
/linux/lib/crypto/
H A DMakefile291 libsha256-y := sha256.o
296 libsha256-y += arm/sha256-ce.o arm/sha256-core.o
297 $(obj)/arm/sha256-core.S: $(src)/arm/sha256-armv4.pl
299 AFLAGS_arm/sha256-core.o += $(aflags-thumb2-y)
303 libsha256-y += arm64/sha256-core.o
304 $(obj)/arm64/sha256-core.S: $(src)/arm64/sha2-armv8.pl
306 libsha256-$(CONFIG_KERNEL_MODE_NEON) += arm64/sha256-ce.o
309 libsha256-$(CONFIG_PPC) += powerpc/sha256-spe-asm.o
310 libsha256-$(CONFIG_RISCV) += riscv/sha256-riscv64-zvknha_or_zvknhb-zvkb.o
312 libsha256-$(CONFIG_X86) += x86/sha256-ssse3-asm.o \
[all …]
H A Dsha256.c3 * SHA-224, SHA-256, HMAC-SHA224, and HMAC-SHA256 library functions
160 #include "sha256.h" /* $(SRCARCH)/sha256.h */
262 void sha256(const u8 *data, size_t len, u8 out[SHA256_DIGEST_SIZE]) in sha256() function
270 EXPORT_SYMBOL(sha256);
342 sha256(raw_key, raw_key_len, derived_key.b); in __hmac_sha256_preparekey()
491 * Implementation Guidance, testing HMAC-SHA256 satisfies the in sha256_mod_init()
500 panic("sha256: FIPS self-test failed\n"); in sha256_mod_init()
514 MODULE_DESCRIPTION("SHA-224, SHA-256, HMAC-SHA224, and HMAC-SHA256 library functions");
/linux/crypto/
H A Dsha256.c3 * 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 Dsha2.h135 * HMAC key and message context structs, shared by HMAC-SHA224 and HMAC-SHA256.
337 * If you don't need incremental computation, consider sha256() instead.
371 * sha256() - Compute SHA-256 message digest in one shot
378 void sha256(const u8 *data, size_t len, u8 out[at_least SHA256_DIGEST_SIZE]);
410 * struct hmac_sha256_key - Prepared key for HMAC-SHA256
418 * struct hmac_sha256_ctx - Context for computing HMAC-SHA256 of a message
426 * hmac_sha256_preparekey() - Prepare a key for HMAC-SHA256
428 * @raw_key: the raw HMAC-SHA256 key
440 * hmac_sha256_init() - Initialize an HMAC-SHA256 context for a new message
455 * hmac_sha256_init_usingrawkey() - Initialize an HMAC-SHA256 context for a new
[all …]
/linux/crypto/asymmetric_keys/
H A Dx509_public_key.c35 /* Calculate a SHA256 hash of the TBS and check it against the in x509_get_sig_params()
38 sha256(cert->tbs, cert->tbs_size, cert->sha256); in x509_get_sig_params()
39 ret = is_hash_blacklisted(cert->sha256, sizeof(cert->sha256), in x509_get_sig_params()
43 (int)sizeof(cert->sha256), cert->sha256); in x509_get_sig_params()
/linux/include/linux/
H A Defi_embedded_fw.h28 * @sha256: SHA256 of the firmware
34 u8 sha256[32]; member
/linux/Documentation/admin-guide/device-mapper/
H A Ddm-crypt.rst25 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 Ddm-ima.rst159 …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/mips/include/asm/octeon/
H A Dcrypto.h8 * 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 DMakefile3 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 DKconfig60 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 Dcrypto.c32 sha256(data, len, hash); in aa_calc_hash()
59 aa_info_message("AppArmor sha256 policy hashing enabled"); in init_profile_hash()
/linux/drivers/crypto/inside-secure/eip93/
H A Deip93-aead.c356 .cra_name = "authenc(hmac(sha256),cbc(aes))",
358 "authenc(hmac(sha256-eip93),cbc(aes-eip93))",
472 .cra_name = "authenc(hmac(sha256),rfc3686(ctr(aes)))",
474 "authenc(hmac(sha256-eip93),rfc3686(ctr(aes-eip93)))",
584 .cra_name = "authenc(hmac(sha256),cbc(des))",
586 "authenc(hmac(sha256-eip93),cbc(des-eip93))",
696 .cra_name = "authenc(hmac(sha256),cbc(des3_ede))",
698 "authenc(hmac(sha256-eip93),cbc(des3_ede-eip93))",
/linux/arch/riscv/purgatory/
H A DMakefile3 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 Dnvidia,tegra234-se-hash.yaml11 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 Dsha256.h3 * 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 Dsha256_asm.S30 SHA256
70 SHA256
/linux/drivers/md/
H A Ddm-ima.h18 #define DM_IMA_TABLE_HASH_ALG "sha256"
42 * Contains the sha256 hashes of the IMA measurements of the target
/linux/drivers/crypto/starfive/
H A Djh7110-hash.c482 alg_name = "sha256-starfive"; in starfive_hash_setkey()
505 return starfive_hash_init_tfm(hash, "sha256-lib", in starfive_sha256_init_tfm()
535 return starfive_hash_init_tfm(hash, "hmac-sha256-lib", in starfive_hmac_sha256_init_tfm()
629 .cra_name = "sha256",
630 .cra_driver_name = "sha256-starfive",
658 .cra_name = "hmac(sha256)",
659 .cra_driver_name = "sha256-hmac-starfive",
/linux/drivers/crypto/ccree/
H A Dcc_hash.h87 * @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 Dsha2-armv8.pl26 # 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/crypto/qce/
H A Dsha.c354 alg_name = "sha256-qce"; in qce_ahash_hmac_setkey()
425 .name = "sha256",
426 .drv_name = "sha256-qce",
443 .name = "hmac(sha256)",
444 .drv_name = "hmac-sha256-qce",

1234567