mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-16 08:44:21 +08:00
a24d22b225
Currently <crypto/sha.h> contains declarations for both SHA-1 and SHA-2, and <crypto/sha3.h> contains declarations for SHA-3. This organization is inconsistent, but more importantly SHA-1 is no longer considered to be cryptographically secure. So to the extent possible, SHA-1 shouldn't be grouped together with any of the other SHA versions, and usage of it should be phased out. Therefore, split <crypto/sha.h> into two headers <crypto/sha1.h> and <crypto/sha2.h>, and make everyone explicitly specify whether they want the declarations for SHA-1, SHA-2, or both. This avoids making the SHA-1 declarations visible to files that don't want anything to do with SHA-1. It also prepares for potentially moving sha1.h into a new insecure/ or dangerous/ directory. Signed-off-by: Eric Biggers <ebiggers@google.com> Acked-by: Ard Biesheuvel <ardb@kernel.org> Acked-by: Jason A. Donenfeld <Jason@zx2c4.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
15 lines
355 B
C
15 lines
355 B
C
/* SPDX-License-Identifier: GPL-2.0 */
|
|
#ifndef ASM_ARM_CRYPTO_SHA1_H
|
|
#define ASM_ARM_CRYPTO_SHA1_H
|
|
|
|
#include <linux/crypto.h>
|
|
#include <crypto/sha1.h>
|
|
|
|
extern int sha1_update_arm(struct shash_desc *desc, const u8 *data,
|
|
unsigned int len);
|
|
|
|
extern int sha1_finup_arm(struct shash_desc *desc, const u8 *data,
|
|
unsigned int len, u8 *out);
|
|
|
|
#endif
|