nvme_insert...ey_versioned(2)

💖 nvme_insert_tls_key_versioned — libnvme API manual, bestie edition 💖

okay so picture this: you're deep in the libnvme API manual (hi, that's the manual this page lives in 🫶) and you need a TLS key derived and inserted like it's nothing. That's this function. She does the math, she drops the key in the keyring, she leaves. Iconic behaviour, no cap. ✨

---

🌸 NAME 🌸

nvme_insert_tls_key_versioned — derive and insert a TLS key, bestie 💅

---

🦋 SYNOPSIS 🦋

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

---

🎀 ARGUMENTS 🎀

• keyring — the keyring we're using, like the lil handbag we keep our keys in 💜
• key_type — the type of the resulting key (what kind of key we're manifesting ✨)
• hostnqn — the Host NVMe Qualified Name
• subsysnqn — the Subsystem NVMe Qualified Name
• version — which key version we're using
• hmac — the HMAC algorithm (the secret sauce for the derivation 🌈)
• configured_key — the configured key data that we derive the key from
• key_len — the length of configured_key. she has measurements, periodt 📏

---

✨ DESCRIPTION ✨

So what does she actually DO? She derives a 'retained' TLS key 💖 — as specified in NVMe TCP 1.0a if version is set to '0', or as specified in NVMe TP8028 if version is set to '1' — and then stores it, as type key_type, in the keyring you specified with keyring.

that's it. that's the whole gig. derive, insert, slay. 🧚

---

💅 RETURN 💅

• the key serial number if the key could be inserted into the keyring 👑
• or 0 with errno otherwise 😭

fr fr, check that errno — a 0 with no follow-up is giving cryptic ex energy and we do not have time for that 🙈

---

and that's the whole page bestie!! mwah 💋 — this one comes to you from the libnvme API manual, dated July 2026. go insert some keys, you've got this 🌟🎀🦋