Home
last modified time | relevance | path

Searched +full:sha +full:- +full:512 (Results 1 – 25 of 55) sorted by relevance

123

/linux/lib/crypto/tests/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-or-later
9 # exist; the BLAKE2s code is always built-in for the /dev/random driver.
20 KUnit tests for the Curve25519 Diffie-Hellman function.
42 tristate "KUnit tests for SHA-1" if !KUNIT_ALL_TESTS
48 KUnit tests for the SHA-1 cryptographic hash function and its
51 # Option is named *_SHA256_KUNIT_TEST, though both SHA-224 and SHA-256 tests are
54 tristate "KUnit tests for SHA-224 and SHA-256" if !KUNIT_ALL_TESTS
60 KUnit tests for the SHA-224 and SHA-256 cryptographic hash functions
63 # Option is named *_SHA512_KUNIT_TEST, though both SHA-384 and SHA-512 tests are
66 tristate "KUnit tests for SHA-384 and SHA-512" if !KUNIT_ALL_TESTS
[all …]
H A Dsha512_kunit.c1 // SPDX-License-Identifier: GPL-2.0-or-later
6 #include "sha512-testvecs.h"
22 #include "hash-test-template.h"
38 MODULE_DESCRIPTION("KUnit tests and benchmark for SHA-512 and HMAC-SHA512");
/linux/include/crypto/
H A Dsha2.h1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Common values for SHA-2 algorithms
76 sctx->state[0] = SHA224_H0; in sha224_block_init()
77 sctx->state[1] = SHA224_H1; in sha224_block_init()
78 sctx->state[2] = SHA224_H2; in sha224_block_init()
79 sctx->state[3] = SHA224_H3; in sha224_block_init()
80 sctx->state[4] = SHA224_H4; in sha224_block_init()
81 sctx->state[5] = SHA224_H5; in sha224_block_init()
82 sctx->state[6] = SHA224_H6; in sha224_block_init()
83 sctx->state[7] = SHA224_H7; in sha224_block_init()
[all …]
/linux/tools/perf/pmu-events/arch/s390/cf_z17/
H A Dpai_crypto.json3 "Unit": "PAI-CRYPTO",
10 "Unit": "PAI-CRYPTO",
14 "PublicDescription": "KM-DEA function ending with CC=0"
17 "Unit": "PAI-CRYPTO",
21 "PublicDescription": "KM-TDEA-128 function ending with CC=0"
24 "Unit": "PAI-CRYPTO",
28 "PublicDescription": "KM-TDEA-192 function ending with CC=0"
31 "Unit": "PAI-CRYPTO",
35 "PublicDescription": "KM-Encrypted-DEA function ending with CC=0"
38 "Unit": "PAI-CRYPTO",
[all …]
/linux/Documentation/ABI/testing/
H A Ddebugfs-pfo-nx-crypto1 What: /sys/kernel/debug/nx-crypto/*
7 These debugfs interfaces are built by the nx-crypto driver, built in
18 The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not
19 recorded here (the hcall will retry until -EBUSY goes away).
36 The total number of bytes hashed by the hardware using SHA-256.
39 The total number of SHA-256 operations submitted to the hardware.
42 The total number of bytes hashed by the hardware using SHA-512.
45 The total number of SHA-512 operations submitted to the hardware.
/linux/fs/crypto/
H A Dhkdf.c1 // SPDX-License-Identifier: GPL-2.0
3 * Implementation of HKDF ("HMAC-based Extract-and-Expand Key Derivation
9 * the case that the fscrypt master keys are hardware-wrapped keys).
18 * SHA-512 because it is well-established, secure, and reasonably efficient.
20 * HKDF-SHA256 was also considered, as its 256-bit security strength would be
21 * sufficient here. A 512-bit security strength is "nice to have", though.
22 * Also, on 64-bit CPUs, SHA-512 is usually just as fast as SHA-256. In the
23 * common case of deriving an AES-256-XTS key (512 bits), that can result in
24 * HKDF-SHA512 being much faster than HKDF-SHA256, as the longer digest size of
25 * SHA-512 causes HKDF-Expand to only need to do one iteration rather than two.
[all …]
/linux/lib/crypto/sparc/
H A Dsha512.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * SHA-512 accelerated using the sparc64 sha512 opcodes
5 * Copyright (c) Jean-Luc Cooke <jlcooke@certainkey.com>
41 pr_info("Using sparc64 sha512 opcode optimized SHA-512/SHA-384 implementation\n"); in sha512_mod_init_arch()
/linux/tools/perf/pmu-events/arch/s390/cf_z16/
H A Dpai_crypto.json3 "Unit": "PAI-CRYPTO",
10 "Unit": "PAI-CRYPTO",
14 "PublicDescription": "KM-DEA function ending with CC=0"
17 "Unit": "PAI-CRYPTO",
21 "PublicDescription": "KM-TDEA-128 function ending with CC=0"
24 "Unit": "PAI-CRYPTO",
28 "PublicDescription": "KM-TDEA-192 function ending with CC=0"
31 "Unit": "PAI-CRYPTO",
35 "PublicDescription": "KM-Encrypted-DEA function ending with CC=0"
38 "Unit": "PAI-CRYPTO",
[all …]
/linux/crypto/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
156 cbc(aes), and the support for the crypto self-tests.
178 bool "Enable cryptographic self-tests"
181 Enable the cryptographic self-tests.
183 The cryptographic self-tests run at boot time, or at algorithm
188 - Development and pre-release testing. In this case, also enable
192 - Production kernels, to help prevent buggy drivers from being used
193 and/or meet FIPS 140-3 pre-operational testing requirements. In
197 bool "Enable the full set of cryptographic self-tests"
200 Enable the full set of cryptographic self-tests for each algorithm.
[all …]
H A Dsha512.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Crypto API support for SHA-384, SHA-512, HMAC-SHA384, and HMAC-SHA512
5 * Copyright (c) Jean-Luc Cooke <jlcooke@certainkey.com>
18 * library SHA context, except the value in bytecount_lo must be block-aligned
36 ctx.bytecount_lo -= partial; in __crypto_sha512_export()
49 ctx->bytecount_lo += *p; in __crypto_sha512_import()
66 /* SHA-384 */
108 return __crypto_sha512_export(&SHA384_CTX(desc)->ctx, out); in crypto_sha384_export()
113 return __crypto_sha512_import(&SHA384_CTX(desc)->ctx, in); in crypto_sha384_import()
118 return __crypto_sha512_export_core(&SHA384_CTX(desc)->ctx, out); in crypto_sha384_export_core()
[all …]
/linux/drivers/crypto/aspeed/
H A DKconfig32 SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, and so on.
45 Supports AES/DES symmetric-key encryption and decryption
/linux/lib/crypto/arm64/
H A Dsha512-ce-core.S1 /* SPDX-License-Identifier: GPL-2.0 */
3 * sha512-ce-core.S - core SHA-384/SHA-512 transform using v8 Crypto Extensions
17 * assemblers both consider the SHA-512 instructions to be part of the
20 * versions.) "sha3" doesn't make a lot of sense, since SHA-512 is part
21 * of the SHA-2 family of algorithms, and also the Arm Architecture
25 .arch armv8-a+sha3
28 * The SHA-512 round constants
102 ld1 {v8.2d-v11.2d}, [x0]
106 ld1 {v20.2d-v23.2d}, [x3], #64
109 0: ld1 {v12.2d-v15.2d}, [x1], #64
[all …]
H A Dsha512.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * arm64-optimized SHA-512 block function
30 data += (nblocks - rem) * SHA512_BLOCK_SIZE; in sha512_blocks()
/linux/lib/crypto/
H A Dsha1.c1 // SPDX-License-Identifier: GPL-2.0
3 * SHA-1 and HMAC-SHA1 library functions
29 * suggested by Artur Skawina - that will also make gcc unable to
50 /* This "rolls" over the 512-bit array */
55 * the input data, the next mix it from the 512-bit array.
73 * sha1_transform - single block SHA1 transform (deprecated)
76 * @data: 512 bits of data to hash
79 * This function executes SHA-1's internal compression function. It updates the
80 * 160-bit internal state (@digest) with a single 512-bit data block (@data).
82 * Don't use this function. SHA-1 is no longer considered secure. And even if
[all …]
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
31 # BLAKE2s support is always built-in, so there's no CRYPTO_LIB_BLAKE2S option.
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.
H A Dsha512.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * SHA-384, SHA-512, HMAC-SHA384, and HMAC-SHA512 library functions
5 * Copyright (c) Jean-Luc Cooke <jlcooke@certainkey.com>
75 u64 a = state->h[0]; in sha512_block_generic()
76 u64 b = state->h[1]; in sha512_block_generic()
77 u64 c = state->h[2]; in sha512_block_generic()
78 u64 d = state->h[3]; in sha512_block_generic()
79 u64 e = state->h[4]; in sha512_block_generic()
80 u64 f = state->h[5]; in sha512_block_generic()
81 u64 g = state->h[6]; in sha512_block_generic()
[all …]
/linux/lib/crypto/riscv/
H A Dsha512.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * SHA-512 and SHA-384 using the RISC-V vector crypto extensions
H A Dsha512-riscv64-zvknhb-zvkb.S1 /* SPDX-License-Identifier: Apache-2.0 OR BSD-2-Clause */
3 // This file is dual-licensed, meaning that you can use it under your
40 // The generated code of this file depends on the following RISC-V extensions:
41 // - RV64I
42 // - RISC-V Vector ('V') with VLEN >= 128
43 // - RISC-V Vector SHA-2 Secure Hash extension ('Zvknhb')
44 // - RISC-V Vector Cryptography Bit-manipulation extension ('Zvkb')
70 // Do 4 rounds of SHA-512. w0 contains the current 4 message schedule words.
73 // computes 4 more message schedule words. w1-w3 contain the next 3 groups of 4
101 // message scheduling. There are 4 words, so an 8-bit mask suffices.
[all …]
/linux/Documentation/admin-guide/
H A Dmodule-signing.rst2 ------------------------------
6 .. - Overview.
7 .. - Configuring module signing.
8 .. - Generating signing keys.
9 .. - Public keys in the kernel.
10 .. - Manually signing modules.
11 .. - Signed modules and stripping.
12 .. - Loading signed modules.
13 .. - Non-valid signatures and unsigned modules.
14 .. - Administering/protecting the private key.
[all …]
/linux/kernel/module/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
64 bool "Debug duplicate modules with auto-loading"
66 Module autoloading allows in-kernel code to request modules through
75 requests are non-fatal virtual memory is a limited resource and each
80 module requests to help identify if module auto-loading may be the
93 non-wait request_module() call is synchronous and waits until modprobe
94 completes. Subsequent auto-loading requests for the same module do
102 abuse was due to module auto-loading. These issues are currently only
105 module auto-loading is not the culprit. There may very well still be
106 many duplicate module auto-loading requests which could be optimized
[all …]
/linux/lib/crypto/mips/
H A Dsha512.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
5 * SHA-512 and SHA-384 Secure Hash Algorithm.
11 * Copyright (c) Jean-Luc Cooke <jlcooke@certainkey.com>
20 * We pass everything as 64-bit. OCTEON can handle misaligned data.
33 write_octeon_64bit_hash_sha512(state->h[0], 0); in sha512_blocks()
34 write_octeon_64bit_hash_sha512(state->h[1], 1); in sha512_blocks()
35 write_octeon_64bit_hash_sha512(state->h[2], 2); in sha512_blocks()
36 write_octeon_64bit_hash_sha512(state->h[3], 3); in sha512_blocks()
37 write_octeon_64bit_hash_sha512(state->h[4], 4); in sha512_blocks()
38 write_octeon_64bit_hash_sha512(state->h[5], 5); in sha512_blocks()
[all …]
/linux/include/linux/
H A Dccp.h1 /* SPDX-License-Identifier: GPL-2.0-only */
27 * ccp_present - check if a CCP device is present
29 * Returns zero if a CCP device is present, -ENODEV otherwise.
34 #define CCP_VMASK ((unsigned int)((1 << CCP_VSIZE) - 1))
39 * ccp_version - get the version of the CCP
46 * ccp_enqueue_cmd - queue an operation for processing by the CCP
55 * result in a return code of -EBUSY.
61 * will be -EINPROGRESS. Any other "err" value during callback is
65 * the return code is -EINPROGRESS or
66 * the return code is -EBUSY and CCP_CMD_MAY_BACKLOG flag is set
[all …]
/linux/lib/crypto/s390/
H A Dsha512.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * SHA-512 optimized using the CP Assist for Cryptographic Functions (CPACF)
/linux/lib/crypto/arm/
H A Dsha512.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * arm32-optimized SHA-512 block function
/linux/lib/crypto/x86/
H A Dsha512.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * x86-optimized SHA-512 block function

123