tpm_buf_append_name(9)

🎀 NAME 🎀

okay so bestie, this page is tpm_buf_append_name(9) from the Kernel API Manual, and it is literally about adding a handle area to the buffer ✨

tpm_buf_append_name — add a handle area to the buffer 💅

---

🌸 SYNOPSIS 🌸

int tpm_buf_append_name (struct tpm_chip *chip , struct tpm_buf *buf ,
       u32 handle , u8 *name );

---

💅 ARGUMENTS 💅

• chip — the TPM chip structure 🫶
• buf — the buffer to be appended 🎀
• handle — the handle to be appended 🔥
• name — the name of the handle (may be NULL) 🌸

---

🦋 DESCRIPTION 🦋

So, to compute session HMACs, we literally need to know the names of the objects that the handles point at 👑

For most objects, this is simply the actual 4 byte handle or an empty buf — and in those cases name should be NULL 💖

But for volatile objects, permanent objects, and NV areas, the name is defined as the hash — using the name algorithm, which should be set to sha256 — of the public area with the two byte algorithm id appended to it ✨ For those objects, the name pointer should point to this 🎯

If a name is required but name is NULL, then TPM2_ReadPublic gets called on the handle to obtain the name 👀

Like most tpm_buf operations, success is assumed — failure comes from an incorrect programming model and gets indicated by a kernel message 💀

🚨 Heads up bestie: it ends the authorization session on failure 😭

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/char/tpm/tpm2-sessions.c 🧚
• tpm_buf_append_hmac_session(9) 💜
• tpm_buf_fill_hmac_session(9) 🦋
• tpm_buf_check_hmac_response(9) 🌸
• tpm2_end_auth_session(9) 🎀
• tpm2_start_auth_session(9) ✨
• tpm2_parse_create_primary(9) 💅
• tpm2_create_primary(9) 🔥
• tpm2_sessions_init(9) 👑

---

mwah 💋 this iconic little page comes from ./drivers/char/tpm, dated October 2026, and it is still tpm_buf_append_name(9) — bye bestie, go slay those handles 🫶💖