ipe_digest_eval(9)

okay so bestie, this is ipe_digest_eval(9) from the Kernel API Manual — the little function that checks one IPE digest against another digest and gives you a clean yes/no. It’s literally a vibe check for two struct digest_info things, except the answer comes back as a bool. 💅

🌸 NAME 🌸

ipe_digest_eval — evaluate an IPE digest against another digest. That’s it, that’s the name section: one digest gets compared against another digest, and you get a match-or-no-match moment. 💖

✨ SYNOPSIS ✨

Here’s the signature, copied exactly because we do not mess with code, bestie:

bool ipe_digest_eval (const struct digest_info *expected , const struct
digest_info *digest );

🎀 ARGUMENTS 🎀

• expected — supplies the policy-provided digest value. This is the digest the policy brought to the comparison table, the reference one, the “this is what we expect” energy. 👑
• digest — supplies the digest to compare against the policy digest value. This is the other one, the one getting held up next to the policy value for the match check. 🦋

🌈 RETURN 🌈

It gives you a bool, and the options are absolutely giving binary:

• true — digests match. Slay, they’re the same. ✅
• false — digests do not match. Not it, bestie. ❌

🔥 SEE ALSO 🔥

Go peek at these, iykyk:

• Kernel file ./security/ipe/digest.c
• ipe_digest_parse(9)
• ipe_digest_free(9)
• ipe_digest_audit(9)

mwah 💋 — this page is from ./security/ipe, dated October 2026, and that’s the whole footer vibe, bestie.