Home
last modified time | relevance | path

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

1234567

/linux/drivers/scsi/mvsas/
H A Dmv_init.c1 // SPDX-License-Identifier: GPL-2.0-only
7 * Copyright 2009-2011 Marvell. <yuxiangl@marvell.com>
17 [chip_6320] = { 1, 2, 0x400, 17, 16, 6, 9, &mvs_64xx_dispatch, },
18 [chip_6440] = { 1, 4, 0x400, 17, 16, 6, 9, &mvs_64xx_dispatch, },
19 [chip_6485] = { 1, 8, 0x800, 33, 32, 6, 10, &mvs_64xx_dispatch, },
22 [chip_9445] = { 1, 4, 0x800, 17, 64, 8, 11, &mvs_94xx_dispatch, },
24 [chip_1300] = { 1, 4, 0x400, 17, 16, 6, 9, &mvs_64xx_dispatch, },
37 .can_queue = 1,
41 .track_queue_depth = 1,
65 struct mvs_phy *phy = &mvi->phy[phy_id]; in mvs_phy_init()
[all …]
/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 …]
/linux/drivers/crypto/ccp/
H A Dccp-crypto-sha.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * AMD Cryptographic Coprocessor (CCP) SHA crypto API support
25 #include "ccp-crypto.h"
37 if (rctx->hash_rem) { in ccp_sha_complete()
39 unsigned int offset = rctx->nbytes - rctx->hash_rem; in ccp_sha_complete()
41 scatterwalk_map_and_copy(rctx->buf, rctx->src, in ccp_sha_complete()
42 offset, rctx->hash_rem, 0); in ccp_sha_complete()
43 rctx->buf_count = rctx->hash_rem; in ccp_sha_complete()
45 rctx->buf_count = 0; in ccp_sha_complete()
49 if (req->result && rctx->final) in ccp_sha_complete()
[all …]
H A Dccp-dev.h1 /* SPDX-License-Identifier: GPL-2.0-only */
19 #include <linux/dma-direction.h>
27 #include "sp-dev.h"
63 /* ------------------------ CCP Version 5 Specifics ------------------------ */
103 #define QUEUE_SIZE_VAL ((ffs(COMMANDS_PER_QUEUE) - 2) & \
105 #define Q_PTR_MASK (2 << (QUEUE_SIZE_VAL + 5) - 1)
125 /* ------------------------ CCP Version 3 Specifics ------------------------ */
147 /* XTS-AES Related Values */
150 /* SHA Related Values */
156 /* Pass-Through Related Values */
[all …]
/linux/include/crypto/
H A Dsha1.h1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Common values for SHA-1 algorithms
30 * An implementation of SHA-1's compression function. Don't use in new code!
31 * You shouldn't be using SHA-1, and even if you *have* to use SHA-1, this isn't
32 * the correct way to hash something with SHA-1 (use crypto_shash instead).
39 /* State for the SHA-1 compression function */
45 * struct sha1_ctx - Context for hashing a message with SHA-1
57 * sha1_init() - Initialize a SHA-1 context for a new message
67 * sha1_update() - Update a SHA-1 context with message data
79 * sha1_final() - Finish computing a SHA-1 message digest
[all …]
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/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/Documentation/devicetree/bindings/crypto/
H A Dsamsung-slimsss.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/crypto/samsung-slimsss.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
14 -- Feeder (FeedCtrl)
15 -- Advanced Encryption Standard (AES) with ECB,CBC,CTR,XTS and (CBC/XTS)/CTS
16 -- SHA-1/SHA-256 and (SHA-1/SHA-256)/HMAC
21 - const: samsung,exynos5433-slim-sss
24 maxItems: 1
[all …]
H A Dsamsung-sss.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/crypto/samsung-sss.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
14 -- Feeder (FeedCtrl)
15 -- Advanced Encryption Standard (AES)
16 -- Data Encryption Standard (DES)/3DES
17 -- Public Key Accelerator (PKA)
18 -- SHA-1/SHA-256/MD5/HMAC (SHA-1/SHA-256/MD5)/PRNG
[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/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/arch/s390/crypto/
H A Dphmac_s390.c1 // SPDX-License-Identifier: GPL-2.0+
45 hwh->walkbytes = crypto_hash_walk_first(req, &hwh->walk); in hwh_prepare()
46 if (hwh->walkbytes < 0) in hwh_prepare()
47 return hwh->walkbytes; in hwh_prepare()
48 hwh->walkaddr = hwh->walk.data; in hwh_prepare()
63 return crypto_hash_walk_done(&hwh->walk, n); in hwh_advance()
65 hwh->walkbytes -= n; in hwh_advance()
66 hwh->walkaddr += n; in hwh_advance()
67 if (hwh->walkbytes > 0) in hwh_advance()
70 hwh->walkbytes = crypto_hash_walk_done(&hwh->walk, 0); in hwh_advance()
[all …]
/linux/lib/crypto/
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
125 default 1
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 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.
58 #define SHA_MIX(t) rol32(W(t+13) ^ W(t+8) ^ W(t+2) ^ W(t), 1)
73 * sha1_transform - single block SHA1 transform (deprecated)
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 …]
/linux/lib/crypto/x86/
H A Dsha1-ni-asm.S2 * Intel SHA Extensions optimized implementation of a SHA-1 update function
58 #define STATE_PTR %rdi /* 1st arg */
97 * Intel SHA Extensions optimized implementation of a SHA-1 block function
99 * This function takes a pointer to the current SHA-1 state, a pointer to the
100 * input data, and the number of 64-byte blocks to process. The number of
H A Dsha256-ni-asm.S2 * Intel SHA Extensions optimized implementation of a SHA-256 update function
58 #define STATE_PTR %rdi /* 1st arg */
83 movdqa (\i-32)*4(SHA256CONSTANTS), MSG
100 * Intel SHA Extensions optimized implementation of a SHA-256 block function
102 * This function takes a pointer to the current SHA-256 state, a pointer to the
103 * input data, and the number of 64-byte blocks to process. Once all blocks
120 * DCBA, HGFE -> ABEF, CDGH
123 movdqu 1*16(STATE_PTR), STATE1 /* HGFE */
163 movdqu STATE0, 1*16(STATE_PTR)
223 // Do 4 rounds of SHA-256 for each of two messages (interleaved). m0_a and m0_b
[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 Dsha256.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Crypto API support for SHA-224, SHA-256, HMAC-SHA224, and HMAC-SHA256
5 * Copyright (c) Jean-Luc Cooke <jlcooke@certainkey.com>
19 * library SHA context, except the value in bytecount must be block-aligned and
27 static_assert(sizeof(struct __sha256_ctx) + 1 == SHA256_SHASH_STATE_SIZE);
36 ctx.bytecount -= partial; in __crypto_sha256_export()
49 ctx->bytecount += *p; in __crypto_sha256_import()
66 /* SHA-224 */
106 return __crypto_sha256_export(&SHA224_CTX(desc)->ctx, out); in crypto_sha224_export()
111 return __crypto_sha256_import(&SHA224_CTX(desc)->ctx, in); in crypto_sha224_import()
[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
27 static_assert(sizeof(struct __sha512_ctx) + 1 == SHA512_SHASH_STATE_SIZE);
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()
[all …]
/linux/lib/crypto/arm64/
H A Dsha256-ce.S1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * sha2-ce-core.S - core SHA-224/SHA-256 transform using v8 Crypto Extensions
12 .arch armv8-a+crypto
51 * The SHA-256 round constants
75 ld1 { v0.4s- v3.4s}, [\tmp], #64
76 ld1 { v4.4s- v7.4s}, [\tmp], #64
77 ld1 { v8.4s-v11.4s}, [\tmp], #64
78 ld1 {v12.4s-v15.4s}, [\tmp]
94 0: ld1 {v16.4s-v19.4s}, [x1], #64
95 sub x2, x2, #1
[all …]
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 …]
/linux/net/sunrpc/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
28 GSS-API mechanism (RFC 1964).
30 Secure RPC calls with Kerberos require an auxiliary user-space
31 daemon which may be found in the Linux nfs-utils package
32 available from http://linux-nfs.org/. In addition, user-space
38 bool "Enable Kerberos enctypes based on AES and SHA-1"
47 SHA-1 digests. These include aes128-cts-hmac-sha1-96 and
48 aes256-cts-hmac-sha1-96.
59 (NIST Special Publication 800-38B). These include
60 camellia128-cts-cmac and camellia256-cts-cmac.
[all …]
/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/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/lib/crypto/sparc/
H A Dsha1.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * SHA-1 accelerated using the sparc64 crypto opcodes
7 * Copyright (c) Jean-Francois Dive <jef@linuxbe.org>
42 pr_info("Using sparc64 sha1 opcode optimized SHA-1 implementation\n"); in sha1_mod_init_arch()

1234567