nvme_import...ey_versioned(2)

💖 nvme_import_tls_key_versioned(2) 💖

okay bestie, so this one is a libnvme API manual page and it's literally called nvme_import_tls_key_versioned — the way this function is just here to tango with your TLS keys? iconic behavior, no notes. 🎀

---

✨ NAME ✨

nvme_import_tls_key_versioned — Import a TLS key 🦋

---

✨ SYNOPSIS ✨

unsigned char * nvme_import_tls_key_versioned (const char *encoded_key ,
       unsigned char *version , unsigned char *hmac , size_t *key_len );

---

✨ ARGUMENTS ✨

• encoded_key — your TLS key, chillin' in PSK interchange format 🌸
• version — tells you which representation of the TLS PSK we're dealing with 👑
• hmac — the HMAC algorithm that's used to transform the configured PSK into a retained PSK 🔥
• key_len — the length of the resulting key data, periodt 📏

---

✨ DESCRIPTION ✨

So basically it imports key_data in the PSK Interchange format — and that format is exactly as defined in section 3.6.1.5 of the NVMe TCP Transport specification. iykyk. 💅

---

✨ RETURN ✨

You get back the raw data of the PSK 🫶 — or NULL with errno set if something went wrong 😭.

bestie, listen: it is the responsibility of the caller to free the returned string. like, that's on you. don't ghost it, free it. 🧚

---

and that's the whole page, no cap. ✨ written for the libnvme API manual, dated July 2026 — love that for us, mwah 💜💖