Home
last modified time | relevance | path

Searched full:md5 (Results 1 – 25 of 155) sorted by relevance

1234567

/linux-6.12.1/tools/testing/selftests/net/tcp_ao/
Dunsigned-md5.c135 try_accept("TCP-AO established: add TCP-MD5 key", (*port)++, NULL, 0, in server_add_fail_tests()
138 try_accept("TCP-MD5 established: add TCP-AO key", (*port)++, &addr_any, in server_add_fail_tests()
159 try_accept("AO server (INADDR_ANY): MD5 client", port++, NULL, 0, in server_fn()
173 try_accept("MD5 server (INADDR_ANY): AO client", port++, &addr_any, 0, in server_fn()
176 try_accept("MD5 server (INADDR_ANY): MD5 client", port++, &addr_any, 0, in server_fn()
178 try_accept("MD5 server (INADDR_ANY): no sign client", port++, &addr_any, in server_fn()
185 try_accept("no sign server: MD5 client", port++, NULL, 0, in server_fn()
191 try_accept("AO+MD5 server: AO client (matching)", port++, in server_fn()
194 try_accept("AO+MD5 server: AO client (misconfig, matching MD5)", port++, in server_fn()
198 try_accept("AO+MD5 server: AO client (misconfig, non-matching)", port++, in server_fn()
[all …]
/linux-6.12.1/arch/sparc/crypto/
Dmd5_glue.c2 /* Glue code for MD5 hashing optimized for sparc64 crypto opcodes.
5 * and crypto/md5.c which are:
22 #include <crypto/md5.h>
145 .cra_name = "md5",
146 .cra_driver_name= "md5-sparc64",
170 pr_info("Using sparc64 md5 opcode optimized MD5 implementation\n"); in md5_sparc64_mod_init()
173 pr_info("sparc64 md5 opcode not available.\n"); in md5_sparc64_mod_init()
186 MODULE_DESCRIPTION("MD5 Message Digest Algorithm, sparc64 md5 opcode accelerated");
188 MODULE_ALIAS_CRYPTO("md5");
DMakefile9 obj-$(CONFIG_CRYPTO_MD5_SPARC64) += md5-sparc64.o
20 md5-sparc64-y := md5_asm.o md5_glue.o
DKconfig30 tristate "Digests: MD5"
35 MD5 message digest algorithm (RFC1321)
Dmd5_asm.S27 MD5
63 MD5
/linux-6.12.1/kernel/
Dgen_kheaders.sh50 # Ignore them for md5 calculation to avoid pointless regeneration.
59 if [ -f kernel/kheaders.md5 ] &&
60 [ "$(head -n 1 kernel/kheaders.md5)" = "$headers_md5" ] &&
61 [ "$(head -n 2 kernel/kheaders.md5 | tail -n 1)" = "$this_file_md5" ] &&
62 [ "$(tail -n 1 kernel/kheaders.md5)" = "$tarfile_md5" ]; then
95 echo $headers_md5 > kernel/kheaders.md5
96 echo "$this_file_md5" >> kernel/kheaders.md5
97 echo "$(md5sum $tarfile | cut -d ' ' -f1)" >> kernel/kheaders.md5
D.gitignore3 /kheaders.md5
/linux-6.12.1/net/sctp/
DKconfig57 when in doubt select 'md5'
60 bool "Enable optional MD5 hmac cookie generation"
62 Enable optional MD5 hmac based SCTP cookie generation
79 bool "Enable optional MD5 hmac cookie generation"
81 Enable optional MD5 hmac based SCTP cookie generation
/linux-6.12.1/arch/powerpc/crypto/
Dmd5-glue.c3 * Glue code for MD5 implementation for PPC assembler
15 #include <crypto/md5.h>
133 .cra_name = "md5",
134 .cra_driver_name= "md5-ppc",
155 MODULE_DESCRIPTION("MD5 Secure Hash Algorithm, PPC assembler");
157 MODULE_ALIAS_CRYPTO("md5");
158 MODULE_ALIAS_CRYPTO("md5-ppc");
DMakefile9 obj-$(CONFIG_CRYPTO_MD5_PPC) += md5-ppc.o
23 md5-ppc-y := md5-asm.o md5-glue.o
DKconfig50 tristate "Digests: MD5"
54 MD5 message digest algorithm (RFC1321)
/linux-6.12.1/tools/testing/selftests/net/packetdrill/
Dtcp_md5_md5-only-on-client-ack.pkt2 // Test what happens when client does not provide MD5 on SYN,
15 // Ooh, weird: client provides MD5 option on the ACK:
16 +.01 < . 1:1(0) ack 1 win 514 <md5 000102030405060708090a0b0c0d0e0f,nop,nop>
17 +.01 < . 1:1(0) ack 1 win 514 <md5 000102030405060708090a0b0c0d0e0f,nop,nop>
/linux-6.12.1/fs/smb/client/
Dcifsencrypt.c120 rc = cifs_alloc_hash("md5", &server->secmech.md5); in cifs_calc_signature()
124 rc = crypto_shash_init(server->secmech.md5); in cifs_calc_signature()
126 cifs_dbg(VFS, "%s: Could not init md5\n", __func__); in cifs_calc_signature()
130 rc = crypto_shash_update(server->secmech.md5, in cifs_calc_signature()
137 return __cifs_calc_signature(rqst, server, signature, server->secmech.md5); in cifs_calc_signature()
439 cifs_dbg(VFS, "%s: Could not init HMAC-MD5, rc=%d\n", __func__, rc); in calc_ntlmv2_hash()
498 cifs_dbg(VFS, "%s: Could not generate MD5 hash, rc=%d\n", __func__, rc); in calc_ntlmv2_hash()
511 /* The MD5 hash starts at challenge_key.key */ in CalcNTLMv2_response()
523 cifs_dbg(VFS, "%s: Could not init HMAC-MD5, rc=%d\n", __func__, rc); in CalcNTLMv2_response()
538 /* Note that the MD5 digest over writes anon.challenge_key.key */ in CalcNTLMv2_response()
[all …]
Dlink.c41 struct shash_desc *md5 = NULL; in symlink_hash() local
43 rc = cifs_alloc_hash("md5", &md5); in symlink_hash()
47 rc = crypto_shash_digest(md5, link_str, link_len, md5_hash); in symlink_hash()
49 cifs_dbg(VFS, "%s: Could not generate md5 hash\n", __func__); in symlink_hash()
50 cifs_free_hash(&md5); in symlink_hash()
80 cifs_dbg(FYI, "%s: MD5 hash failure: %d\n", __func__, rc); in parse_mf_symlink()
119 cifs_dbg(FYI, "%s: MD5 hash failure: %d\n", __func__, rc); in format_mf_symlink()
/linux-6.12.1/arch/mips/cavium-octeon/crypto/
Docteon-md5.c4 * MD5 Message Digest Algorithm (RFC1321).
8 * Based on crypto/md5.c, which is:
22 #include <crypto/md5.h>
183 .cra_name = "md5",
184 .cra_driver_name= "octeon-md5",
207 MODULE_DESCRIPTION("MD5 Message Digest Algorithm (OCTEON)");
Docteon-crypto.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-6.12.1/tools/testing/selftests/net/
Dfcnal-test.sh867 # MD5 tests without VRF
880 log_test $? 0 "MD5: Single address config"
882 # client sends MD5, server not configured
884 show_hint "Should timeout due to MD5 mismatch"
888 log_test $? 2 "MD5: Server no config, client uses password"
896 log_test $? 2 "MD5: Client uses wrong password"
900 show_hint "Should timeout due to MD5 mismatch"
904 log_test $? 2 "MD5: Client address does not match address configured with password"
907 # MD5 extension - prefix length
915 log_test $? 0 "MD5: Prefix config"
[all …]
/linux-6.12.1/drivers/crypto/caam/
Dkey_gen.h11 * @hash: Hashing algorithm selection, one of OP_ALG_ALGSEL_* - MD5, SHA1,
18 /* Sizes for MDHA pads (*not* keys): MD5, SHA1, 224, 256, 384, 512 */ in split_key_len()
29 * @hash: Hashing algorithm selection, one of OP_ALG_ALGSEL_* - MD5, SHA1,
/linux-6.12.1/Documentation/networking/
Dtcp_ao.rst11 The intent of TCP-AO is to deprecate TCP-MD5 providing better security,
17 .. table:: Short and Limited Comparison of TCP-AO and TCP-MD5
20 | | TCP-MD5 | TCP-AO |
22 |Supported hashing |MD5 |Must support HMAC-SHA1 |
205 Q: Can TCP-MD5 connection migrate to TCP-AO (and vice-versa):
209 TCP MD5-protected connections cannot be migrated to TCP-AO because TCP MD5
245 to TCP-MD5. It means that a userspace application that wants to use TCP-AO
255 ``setsockopt()s`` for TCP-MD5 support.
364 In contrast with an established TCP-MD5 connection which has just one key,
387 This is a similar "do-nothing" approach to TCP-MD5 from the kernel side and
[all …]
/linux-6.12.1/crypto/
Dmd5.c4 * MD5 Message Digest Algorithm (RFC1321).
19 #include <crypto/md5.h>
228 .cra_name = "md5",
229 .cra_driver_name = "md5-generic",
249 MODULE_DESCRIPTION("MD5 Message Digest Algorithm");
250 MODULE_ALIAS_CRYPTO("md5");
/linux-6.12.1/arch/mips/crypto/
DKconfig24 tristate "Digests: MD5 (OCTEON)"
29 MD5 message digest algorithm (RFC1321)
/linux-6.12.1/Documentation/devicetree/bindings/crypto/
Dsamsung-sss.yaml18 -- SHA-1/SHA-256/MD5/HMAC (SHA-1/SHA-256/MD5)/PRNG
/linux-6.12.1/drivers/crypto/ccree/
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-6.12.1/include/net/
Ddropreason-core.h163 * @SKB_DROP_REASON_TCP_AUTH_HDR: TCP-MD5 or TCP-AO hashes are met
168 * @SKB_DROP_REASON_TCP_MD5NOTFOUND: no MD5 hash and one expected,
173 * @SKB_DROP_REASON_TCP_MD5UNEXPECTED: MD5 hash and we're not expecting
178 * @SKB_DROP_REASON_TCP_MD5FAILURE: MD5 hash and its wrong, corresponding
/linux-6.12.1/drivers/crypto/
DKconfig308 tristate "Support for OMAP MD5/SHA1/SHA2 hw accelerator"
317 OMAP processors have MD5/SHA1/SHA2 hw accelerator. Select this if you
318 want to use the OMAP module for MD5/SHA1/SHA2 algorithms.
393 Select this to offload Exynos from HASH MD5/SHA1/SHA256.
394 This will select software SHA1, MD5 and SHA256 as they are
676 hardware hash accelerator. Supporting MD5/SHA1/SHA224/SHA256

1234567