summaryrefslogtreecommitdiffstats
path: root/pbl
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2022-08-18 07:04:45 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2022-08-22 10:52:19 +0200
commit4794b2ccced53efaf2dc8d0fc1c70e71431d4daa (patch)
tree0ad644cd658ea43fbcaa9d0d04347555b2adda14 /pbl
parent4b5b65fe21be09d5eb42ab822c72638a110b7c60 (diff)
downloadbarebox-4794b2ccced53efaf2dc8d0fc1c70e71431d4daa.tar.gz
barebox-4794b2ccced53efaf2dc8d0fc1c70e71431d4daa.tar.xz
pbl: export pbl_barebox_verify
There's no downside to always build the digest verification code in PBL and export pbl_barebox_verify to access it. This allows board code to use the function for verifying other firmware blobs and CONFIG_PBL_VERIFY_PIGGY=y will remain to enable the verification at barebox proper extraction time. Code not using it will have the function sections garbage collected by the linker, so no functional change. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220818050447.2072932-2-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'pbl')
-rw-r--r--pbl/decomp.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/pbl/decomp.c b/pbl/decomp.c
index 1e0ef81ada..553895bac5 100644
--- a/pbl/decomp.c
+++ b/pbl/decomp.c
@@ -54,14 +54,14 @@ static void noinline errorfn(char *error)
extern unsigned char sha_sum[];
extern unsigned char sha_sum_end[];
-static int pbl_barebox_verify(void *compressed_start, unsigned int len, void *hash,
- unsigned int hash_len)
+int pbl_barebox_verify(const void *compressed_start, unsigned int len,
+ const void *hash, unsigned int hash_len)
{
struct sha256_state sha_state = { 0 };
struct digest d = { .ctx = &sha_state };
char computed_hash[SHA256_DIGEST_SIZE];
int i;
- char *char_hash = hash;
+ const char *char_hash = hash;
if (hash_len != SHA256_DIGEST_SIZE)
return -1;