STRUCT SECRET_HEADER(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct secret_header(9) πŸ’–

okay bestie, so this is a kernel API manual page for struct secret_header, and it's literally the glow-up your day needed. buckle in πŸŽ€


✨ NAME ✨

struct secret_header β€” it's the header of the entire secret area πŸ‘‘ and the vibe is that this thing should be followed by instances of struct secret_entry. like, header first, entries after, no cap. πŸ¦‹


✨ SYNOPSIS ✨

struct secret_header {
    efi_guid_t guid;
    u32 len;
 };

look at her. two members. iconic. πŸ’…


✨ Members ✨

  • guid β€” this one must be EFI_SECRET_TABLE_HEADER_GUID. not "should", not "maybe", must. it's giving strict queen energy πŸ‘‘ so don't try anything cute with it.
  • len β€” the length in bytes of the entire secret area, including the header. yes, including the header, bestie. the whole thing. don't forget to count the header itself or the math will not eat πŸ’€

🌸 SEE ALSO 🌸

  • Kernel file ./drivers/virt/coco/efi_secret/efi_secret.c
  • efi_secret: Allow reading EFI confidential computing (coco) secret area(9)
  • struct secret_entry(9)

fr fr go read those next, they're the supporting cast and they understood the assignment 🫢


🌈 lowkey a reminder: guid has exactly one legal value and len covers the whole area, header included. those two facts are doing all the heavy lifting here, so don't sleep on them πŸ’œ

and that's the page, bestie!! πŸ’–βœ¨ source/version is ./drivers/virt/coco/efi_secret, dated October 2026, and the manual is struct secret_header(9) β€” mwah, take care, drink water, and may your secret areas always be correctly sized πŸŽ€πŸ§šπŸ“

πŸ“¦ where this page comes from