| /linux/include/crypto/ |
| H A D | sha2.h | 135 * HMAC key and message context structs, shared by HMAC-SHA224 and HMAC-SHA256. 206 * struct hmac_sha224_key - Prepared key for HMAC-SHA224 214 * struct hmac_sha224_ctx - Context for computing HMAC-SHA224 of a message 222 * hmac_sha224_preparekey() - Prepare a key for HMAC-SHA224 224 * @raw_key: the raw HMAC-SHA224 key 236 * hmac_sha224_init() - Initialize an HMAC-SHA224 context for a new message 237 * @ctx: (output) the HMAC context to initialize 238 * @key: the prepared HMAC key 251 * hmac_sha224_init_usingrawkey() - Initialize an HMAC-SHA224 context for a new 253 * @ctx: (output) the HMAC context to initialize [all …]
|
| H A D | sha1.h | 100 * struct hmac_sha1_key - Prepared key for HMAC-SHA1 110 * struct hmac_sha1_ctx - Context for computing HMAC-SHA1 of a message 120 * hmac_sha1_preparekey() - Prepare a key for HMAC-SHA1 122 * @raw_key: the raw HMAC-SHA1 key 134 * hmac_sha1_init() - Initialize an HMAC-SHA1 context for a new message 135 * @ctx: (output) the HMAC context to initialize 136 * @key: the prepared HMAC key 145 * hmac_sha1_init_usingrawkey() - Initialize an HMAC-SHA1 context for a new 147 * @ctx: (output) the HMAC context to initialize 148 * @raw_key: the raw HMAC-SHA1 key [all …]
|
| H A D | md5.h | 92 * struct hmac_md5_key - Prepared key for HMAC-MD5 102 * struct hmac_md5_ctx - Context for computing HMAC-MD5 of a message 112 * hmac_md5_preparekey() - Prepare a key for HMAC-MD5 114 * @raw_key: the raw HMAC-MD5 key 126 * hmac_md5_init() - Initialize an HMAC-MD5 context for a new message 127 * @ctx: (output) the HMAC context to initialize 128 * @key: the prepared HMAC key 137 * hmac_md5_init_usingrawkey() - Initialize an HMAC-MD5 context for a new 139 * @ctx: (output) the HMAC context to initialize 140 * @raw_key: the raw HMAC-MD5 key [all …]
|
| /linux/fs/ubifs/ |
| H A D | auth.c | 38 * ubifs_hash_calc_hmac - calculate a HMAC from a hash 40 * @hash: the node to calculate a HMAC for 41 * @hmac: the returned HMAC 46 u8 *hmac) in ubifs_hash_calc_hmac() argument 48 return crypto_shash_tfm_digest(c->hmac_tfm, hash, c->hash_len, hmac); in ubifs_hash_calc_hmac() 58 * It creates a HMAC from the given input hash and writes it to the node. 80 err = ubifs_hash_calc_hmac(c, hash, auth->hmac); in ubifs_prepare_auth_node() 275 snprintf(hmac_name, CRYPTO_MAX_ALG_NAME, "hmac(%s)", in ubifs_init_authentication() 326 ubifs_err(c, "hmac %s is bigger than maximum allowed hmac size (%d > %d)", in ubifs_init_authentication() 376 * ubifs_node_calc_hmac - calculate the HMAC of a UBIFS node [all …]
|
| /linux/net/sctp/ |
| H A D | Kconfig | 61 If unsure, choose the default (HMAC-SHA256). 64 bool "HMAC-SHA256"
|
| /linux/Documentation/ABI/testing/ |
| H A D | evm | 8 HMAC-sha1 value across the extended attributes, storing the 12 an HMAC-sha1 generated locally with a 24 0 Enable HMAC validation and creation 27 runtime. Not supported if HMAC validation and 36 will enable HMAC validation and creation 42 will enable HMAC and digital signature validation and 43 HMAC creation and disable all further modification of policy. 72 Note that once an HMAC key has been loaded, it will no longer 74 HMAC key has been loaded will clear the corresponding flag. 81 Loading an HMAC key is the only way to disable metadata
|
| /linux/drivers/crypto/caam/ |
| H A D | caamalg.c | 2140 .cra_name = "authenc(hmac(md5)," 2142 .cra_driver_name = "authenc-hmac-md5-" 2164 .cra_name = "authenc(hmac(sha1)," 2166 .cra_driver_name = "authenc-hmac-sha1-" 2188 .cra_name = "authenc(hmac(sha224)," 2190 .cra_driver_name = "authenc-hmac-sha224-" 2212 .cra_name = "authenc(hmac(sha256)," 2214 .cra_driver_name = "authenc-hmac-sha256-" 2236 .cra_name = "authenc(hmac(sha384)," 2238 .cra_driver_name = "authenc-hmac-sha384-" [all …]
|
| H A D | caamalg_qi.c | 1653 .cra_name = "authenc(hmac(md5),cbc(aes))", 1654 .cra_driver_name = "authenc-hmac-md5-" 1674 .cra_name = "echainiv(authenc(hmac(md5)," 1676 .cra_driver_name = "echainiv-authenc-hmac-md5-" 1697 .cra_name = "authenc(hmac(sha1),cbc(aes))", 1698 .cra_driver_name = "authenc-hmac-sha1-" 1718 .cra_name = "echainiv(authenc(hmac(sha1)," 1721 "hmac-sha1-cbc-aes-caam-qi", 1741 .cra_name = "authenc(hmac(sha224),cbc(aes))", 1742 .cra_driver_name = "authenc-hmac-sha224-" [all …]
|
| /linux/security/integrity/evm/ |
| H A D | Kconfig | 22 Include filesystem UUID for HMAC calculation. 27 WARNING: changing the HMAC calculation method or adding 36 Include additional SMACK xattrs for HMAC calculation. 40 in the HMAC calculation, enabling this option includes newly defined 44 WARNING: changing the HMAC calculation method or adding 53 Allow userland to provide additional xattrs for HMAC calculation.
|
| H A D | evm_main.c | 105 pr_info("HMAC attrs: 0x%x\n", evm_hmac_attrs); in evm_init_config() 115 * errors, based on the ability of EVM to calculate HMACs. If the HMAC key 166 * evm_verify_hmac - calculate and compare the HMAC with the EVM xattr 168 * Compute the HMAC on the dentry's protected set of extended attributes 173 * HMAC.) 412 * Calculate the HMAC for the given dentry and verify it against the stored 414 * previously retrieved to calculate the HMAC. 526 /* Exception if the HMAC is not going to be calculated. */ in evm_protect_xattr() 546 /* Exception if the HMAC is not going to be calculated. */ in evm_protect_xattr() 583 * access to the EVM encrypted key needed to calculate the HMAC, prevent [all …]
|
| H A D | evm_crypto.c | 10 * Using root's kernel master key (kmk), calculate the HMAC 38 static const char evm_hmac[] = "hmac(sha1)"; 41 * evm_set_key() - set EVM HMAC key from the kernel 45 * This function allows setting the EVM HMAC key from the kernel 83 pr_err_once("HMAC key is not set\n"); in init_desc() 161 /* The hmac uid and gid must be encoded in the initial user in hmac_add_misc() 214 * Calculate the HMAC value across the set of protected security xattrs. 217 * the hmac using the requested xattr value. Don't alloc/free memory for 362 * Calculate the hmac and update security.evm xattr 424 * Get the key from the TPM for the SHA1-HMAC
|
| /linux/Documentation/networking/ |
| H A D | seg6-sysctl.rst | 20 Define HMAC policy for ingress SR-enabled packets on this interface. 22 * -1 - Ignore HMAC field 23 * 0 - Accept SR packets without HMAC, validate SR packets with HMAC 24 * 1 - Drop SR packets without HMAC, validate SR packets with HMAC
|
| /linux/crypto/ |
| H A D | sha256.c | 3 * Crypto API support for SHA-224, SHA-256, HMAC-SHA224, and HMAC-SHA256 182 /* HMAC-SHA224 */ 249 /* HMAC-SHA256 */ 356 .base.cra_name = "hmac(sha224)", 357 .base.cra_driver_name = "hmac-sha224-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"); 416 MODULE_ALIAS_CRYPTO("hmac(sha224)"); 417 MODULE_ALIAS_CRYPTO("hmac-sha224-lib"); [all …]
|
| H A D | sha512.c | 3 * Crypto API support for SHA-384, SHA-512, HMAC-SHA384, and HMAC-SHA512 188 /* HMAC-SHA384 */ 255 /* HMAC-SHA512 */ 362 .base.cra_name = "hmac(sha384)", 363 .base.cra_driver_name = "hmac-sha384-lib", 382 .base.cra_name = "hmac(sha512)", 383 .base.cra_driver_name = "hmac-sha512-lib", 416 MODULE_DESCRIPTION("Crypto API support for SHA-384, SHA-512, HMAC-SHA384, and HMAC-SHA512"); 422 MODULE_ALIAS_CRYPTO("hmac(sha384)"); 423 MODULE_ALIAS_CRYPTO("hmac-sha384-lib"); [all …]
|
| H A D | md5.c | 3 * Crypto API support for MD5 and HMAC-MD5 197 .base.cra_name = "hmac(md5)", 198 .base.cra_driver_name = "hmac-md5-lib", 231 MODULE_DESCRIPTION("Crypto API support for MD5 and HMAC-MD5"); 235 MODULE_ALIAS_CRYPTO("hmac(md5)"); 236 MODULE_ALIAS_CRYPTO("hmac-md5-lib");
|
| /linux/drivers/char/tpm/ |
| H A D | tpm2-sessions.c | 7 * authorization HMAC and request response encryption. 9 * The idea is to ensure that every TPM command is HMAC protected by a 36 * The design is all the crypto, hash and hmac gunk is confined in this 50 * calculating the HMAC. In particular, for NV, volatile and 52 * tpm_buf_append_hmac_session() which appends the hmac session to the 56 * command buffer is finalized so it can fill in the correct HMAC 123 * because several HMAC/KDF schemes use the combination of the 302 * for the HMAC which cannot be computed until the command buffer is 312 * tpm_buf_fill_hmac_session() otherwise the HMAC will be incorrect 341 * before computing the HMAC in tpm_buf_append_hmac_session() [all …]
|
| /linux/lib/crypto/ |
| H A D | Kconfig | 82 The MD5 and HMAC-MD5 library functions. Select this if your module 136 The SHA-1 and HMAC-SHA1 library functions. Select this if your module 153 The SHA-224, SHA-256, HMAC-SHA224, and HMAC-SHA256 library functions. 172 The SHA-384, SHA-512, HMAC-SHA384, and HMAC-SHA512 library functions.
|
| /linux/net/sunrpc/auth_gss/ |
| H A D | gss_krb5_crypto.c | 158 * @cksumout: OUT: a buffer to be filled in with the computed HMAC 160 * Usually expressed as H = HMAC(K, message)[1..h] . 586 struct xdr_netobj hmac; in gss_krb5_aes_encrypt() local 625 hmac.len = kctx->gk5e->cksumlength; in gss_krb5_aes_encrypt() 626 hmac.data = buf->tail[0].iov_base + buf->tail[0].iov_len; in gss_krb5_aes_encrypt() 633 * the hmac. in gss_krb5_aes_encrypt() 639 offset + GSS_KRB5_TOK_HDR_LEN, &hmac); in gss_krb5_aes_encrypt() 650 /* Now update buf to account for HMAC */ in gss_krb5_aes_encrypt() 694 /* Get the packet's hmac value */ in gss_krb5_aes_decrypt() 718 * @cksumout: OUT: a buffer to be filled in with the computed HMAC [all …]
|
| /linux/Documentation/devicetree/bindings/crypto/ |
| H A D | nvidia,tegra234-se-hash.yaml | 12 HMAC(SHA224), HMAC(SHA256), HMAC(SHA384), HMAC(SHA512)
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm-security.rst | 60 The first can be thwarted by always doing HMAC protection of the PCR 62 substituted without producing a detectable HMAC failure in the 72 interception which HMAC protection alone cannot protect against, so 131 All TPM commands the kernel uses allow sessions. HMAC sessions may be 134 HMAC and encryption keys are usually derived from the shared 136 known (and usually empty). Thus, every HMAC session used by the 144 session may also be reused for the in-kernel HMAC, encryption and 150 For every in-kernel operation we use null primary salted HMAC to 189 decryption HMAC session salted to the EK primary (which also does not 193 succeeds and the HMAC verifies on return we know we have a loadable
|
| /linux/net/ipv6/ |
| H A D | seg6_hmac.c | 3 * SR-IPv6 implementation -- HMAC functions 114 /* Let's build the HMAC text on the ring buffer. The text is composed in __hmac_get_algo() 120 * 4. HMAC Key ID (32 bits) in __hmac_get_algo() 139 /* HMAC Key ID */ in __do_hmac() 171 /* checks if an incoming SR-enabled packet's HMAC status matches in seg6_hmac_compute() 214 if (crypto_memneq(hmac_output, tlv->hmac, SEG6_HMAC_FIELD_LEN)) in seg6_hmac_compute() 297 memset(tlv->hmac, 0, SEG6_HMAC_FIELD_LEN); in seg6_hmac_info_lookup() 298 err = seg6_hmac_compute(hinfo, srh, saddr, tlv->hmac); in seg6_hmac_info_lookup()
|
| /linux/net/mptcp/ |
| H A D | crypto_test.c | 35 char hmac[32], hmac_hex[65]; in mptcp_crypto_test_basic() local 42 /* mptcp hmap will convert to be before computing the hmac */ in mptcp_crypto_test_basic() 51 mptcp_crypto_hmac_sha(key1, key2, msg, 8, hmac); in mptcp_crypto_test_basic() 53 sprintf(&hmac_hex[j << 1], "%02x", hmac[j] & 0xff); in mptcp_crypto_test_basic()
|
| /linux/lib/crypto/tests/ |
| H A D | hash-test-template.h | 469 #ifdef HMAC 471 * Test the corresponding HMAC variant. 473 * This test case is fairly short, since HMAC is just a simple C wrapper around 476 * interrupt context again for HMAC, nor to have a long list of test vectors. 480 * a key length, generate the inputs from a seed, and compute the HMAC value. 481 * Concatenate all these HMAC values together, and compute the HMAC of that. 482 * Verify that value. If this fails, then the HMAC implementation is wrong. 518 /* Verify that HMAC() is consistent with HMAC_USINGRAWKEY(). */ in test_hmac() 520 HMAC(&key, test_buf, data_len, mac2); in test_hmac() 523 "HMAC gave different results with raw and prepared keys"); in test_hmac() [all …]
|
| /linux/tools/perf/pmu-events/arch/s390/cf_z17/ |
| H A D | pai_crypto.json | 1133 "BriefDescription": "KMAC HMAC SHA 224", 1134 "PublicDescription": "KMAC-HMAC-SHA-224 function ending with CC=0" 1140 "BriefDescription": "KMAC HMAC SHA 256", 1141 "PublicDescription": "KMAC-HMAC-SHA-256 function ending with CC=0" 1147 "BriefDescription": "KMAC HMAC SHA 384", 1148 "PublicDescription": "KMAC-HMAC-SHA-384 function ending with CC=0" 1154 "BriefDescription": "KMAC HMAC SHA 512", 1155 "PublicDescription": "KMAC-HMAC-SHA-512 function ending with CC=0" 1161 "BriefDescription": "KMAC HMAC ENCRYPTED SHA 224", 1162 "PublicDescription": "KMAC-HMAC-Encrypted-SHA-224 function ending with CC=0" [all …]
|
| /linux/drivers/crypto/intel/keembay/ |
| H A D | Kconfig | 73 sm3, as well as the HMAC variant of these algorithms. 81 bool "Enable sha224 and hmac(sha224) support in Intel Keem Bay OCS HCU" 84 Enables support for sha224 and hmac(sha224) algorithms in the Intel 88 Provides OCS HCU hardware acceleration of sha224 and hmac(224).
|