nvme_insert_tls_key_compat(9)

✨ nvme_insert_tls_key_compat(9) ✨

okay bestie, sit down, hydrate, because we're doing libnvme API manual energy today and this one is genuinely a little ✨special✨ — it's the compat girlie, the one that does things the old way. iykyk 💅

---

🌸 NAME 🌸

nvme_insert_tls_key_compat — derive and insert TLS key 🎀

---

🦋 SYNOPSIS 🦋

long nvme_insert_tls_key_compat (const char *keyring , const char
*key_type , const char *hostnqn , const char *subsysnqn , int version ,
int hmac , unsigned char *configured_key , int key_len );

no cap, that's the whole signature. every pointer, every int, all of it, untouched 💖

---

💜 ARGUMENTS 💜

• keyring — the keyring to use 🗝️ like, where the key is gonna live
• key_type — the type of the resulting key (yes, the resulting one, not the input, pay attention bestie)
• hostnqn — Host NVMe Qualified Name 🏠
• subsysnqn — Subsystem NVMe Qualified Name 🧩
• version — which key version to use
• hmac — the HMAC algorithm
• configured_key — the configured key data you're deriving the key from 🔑
• key_len — length of configured_key 📏

---

🌈 DESCRIPTION 🌈

so here's the tea ☕ — this function derives a 'retained' TLS key exactly as specified in NVMe TCP 1.0a (that's when version is set to 0) or in NVMe TP8028 (that's when version is set to 1), and then stores it as type key_type in the keyring specified by keyring. periodt. 💅

and this version — the _compat one, the main character of this page — differs from nvme_insert_tls_key_versioned in one specific way: it uses the original implementation for HKDF Expand-Label, which does not prefix the 'info' and 'label' strings with the length. 🫶

not me being the legacy-behaviour one... but fr fr, if you need the no-length-prefix behaviour, this is your girl. don't come for the new one and expect the old strings, iykyk 💀

---

⭐ RETURN ⭐

the key serial number if the key could be inserted into the keyring… or 0 with errno otherwise. 🙈

like, 0 = it did not slay. check errno, bestie, she'll tell you what happened. 🔥

---

and that's the whole page, no notes, we ate 🍓✨ — this was the libnvme API manual, dated August 2026, and yes it's still calling itself nvme_insert_tls_key_compat(9) in the footer because it knows exactly who it is. mwah. 💖🧚‍♀️👑