mirror of
https://codeberg.org/libreboot/lbmk.git
synced 2026-03-26 22:09:03 +02:00
i currently use the output of sha512sum in several places of xbmk, which is a bit unreliable in case output changes. other cases where i use util outputs in variables are probably reliable, because i'm using mostly posix utilities in those. to mitigate this, i now import suckless sbase, which has a reasonable sha512sum implementation. *every* binary it builds is being placed in build.list, because i'll probably start using more of them. for example, i may start modifying the "date" implementation, adding the GNU-specific options that i need as mentioned on init.sh i'm importing it in util/ because the sha512sum util is needed for verifying project sources, so if sbase itself is a "project source", that means we can into a chicken and egg bootstrapping problem. this is sbase at revision: 055cc1ae1b3a13c3d8f25af0a4a3316590efcd48 Signed-off-by: Leah Rowe <leah@libreboot.org>
27 lines
593 B
C
27 lines
593 B
C
/* public domain sha384 implementation based on fips180-3 */
|
|
#include <stdint.h>
|
|
#include "../sha384.h"
|
|
|
|
extern void sha512_sum_n(void *, uint8_t *, int n);
|
|
|
|
void
|
|
sha384_init(void *ctx)
|
|
{
|
|
struct sha384 *s = ctx;
|
|
s->len = 0;
|
|
s->h[0] = 0xcbbb9d5dc1059ed8ULL;
|
|
s->h[1] = 0x629a292a367cd507ULL;
|
|
s->h[2] = 0x9159015a3070dd17ULL;
|
|
s->h[3] = 0x152fecd8f70e5939ULL;
|
|
s->h[4] = 0x67332667ffc00b31ULL;
|
|
s->h[5] = 0x8eb44a8768581511ULL;
|
|
s->h[6] = 0xdb0c2e0d64f98fa7ULL;
|
|
s->h[7] = 0x47b5481dbefa4fa4ULL;
|
|
}
|
|
|
|
void
|
|
sha384_sum(void *ctx, uint8_t md[SHA384_DIGEST_LENGTH])
|
|
{
|
|
sha512_sum_n(ctx, md, 6);
|
|
}
|