nvme_import_tls_key(2)

💖 nvme_import_tls_key — the libnvme API manual, bestie edition ✨

okay so hi bestie!! 🫶 welcome to nvme_import_tls_key(2) from the libnvme API manual. this is the one that takes your cute little encoded TLS key and turns it into the actual raw bytes your code can use. it's giving "glow up but for key material" 💅

---

🌸 NAME 🌸

nvme_import_tls_key — import a TLS key 🔑

---

✨ SYNOPSIS ✨

unsigned char * nvme_import_tls_key (const char *encoded_key , int
*key_len , unsigned int *hmac );

like yes, that's the whole signature, no cap. 📜

---

🎀 ARGUMENTS 🎀

• encoded_key — the TLS key, but in PSK interchange format. that's the text-y version, not the raw bytes yet 🦋
• key_len — this is where the length of the resulting key data goes. output girlie, she reports back 📏
• hmac — the HMAC algorithm. which flavor of HMAC we're dealing with 🔐

---

🧚 DESCRIPTION 🧚

so basically this function imports key_data in the PSK Interchange format — and the lore for that format is defined in section 3.6.1.5 of the NVMe TCP Transport specification 📖✨. that spec is the source of truth, we do not freestyle it, periodt.

you hand it the interchange-format key, it hands you back the raw key data. the way that encoding works is literally spelled out in the spec so go read that section if you're curious, iykyk 💜

---

👑 RETURN 👑

it returns the raw data of the PSK 🌈 — or NULL with errno set if something went wrong 😭 (yes, errno, the classic).

⚠️ heads up bestie: it is the responsibility of the caller to free the returned string. that memory is yours now. don't ghost it, free() it. fr fr.

---

🦋 SEE ALSO 🦋

there's no SEE ALSO section in this one — it's a short queen, she said what she said 💅

---

<div>okay bye ily, this page was brought to you by libnvme and the fine folks who dated it July 2026 🌸✨ mwah, go free your strings 🎀🫶</div>