forked from mirrors/linux
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>
24 lines
590 B
C
24 lines
590 B
C
/* SPDX-License-Identifier: GPL-2.0 */
|
|
#ifndef _LINUX_PURGATORY_H
|
|
#define _LINUX_PURGATORY_H
|
|
|
|
#include <linux/types.h>
|
|
#include <crypto/sha2.h>
|
|
#include <uapi/linux/kexec.h>
|
|
|
|
struct kexec_sha_region {
|
|
unsigned long start;
|
|
unsigned long len;
|
|
};
|
|
|
|
/*
|
|
* These forward declarations serve two purposes:
|
|
*
|
|
* 1) Make sparse happy when checking arch/purgatory
|
|
* 2) Document that these are required to be global so the symbol
|
|
* lookup in kexec works
|
|
*/
|
|
extern struct kexec_sha_region purgatory_sha_regions[KEXEC_SEGMENT_MAX];
|
|
extern u8 purgatory_sha256_digest[SHA256_DIGEST_SIZE];
|
|
|
|
#endif
|