LIBNVMF_INSERT_TLS_KEY_VERSIONED-LIBNVME3(2)

📦 version 3.2, in arch rolling

💖 NAME 💖

okay so bestie, welcome to the libnvme API manual ✨ this page is all about libnvmf_insert_tls_key_versioned(9) — and its whole name is literally libnvmf_insert_tls_key_versioned — Derive and insert a TLS PSK. That's the assignment. 💅

🌸 SYNOPSIS 🌸

int libnvmf_insert_tls_key_versioned (struct libnvme_global_ctx *ctx ,
const char *keyring , const char *key_type , const char *hostnqn , const
char *subsysnqn , int version , enum libnvmf_hmac_alg hmac , unsigned
char *configured_key , int key_len , long *key );

🎀 ARGUMENTS 🎀

  • ctx — the struct libnvme_global_ctx object 🫶
  • keyring — the keyring to use 🔑
  • key_type — the type of the resulting key ✨
  • hostnqn — the Host NVMe Qualified Name 💖
  • subsysnqn — the Subsystem NVMe Qualified Name 🌈
  • version — the TLS PSK identity version to use 🎀
  • hmac — the HMAC algorithm 🧚
  • configured_key — the configured PSK to derive the retained PSK from 🔥
  • key_len — the length of configured_key 📏
  • key — the key serial to return 👑

🦋 DESCRIPTION 🦋

so here's the vibe, bestie: this function derives a retained PSK from configured_key and, from that, the TLS PSK and its identity as specified in the NVMe TCP Transport Specification 1.3, section 3.6.1.3. Then it stores the TLS PSK as type key_type under that identity in the keyring specified by keyring. iconic behavior, no cap 💅✨

the version argument selects the identity version: 0 is obsolete and defined in the NVMe TCP Transport Specification 1.0, and 1 is TLS 1.3 with the PSK digest in the identity.

🚨 heads up: version 0 is obsolete, so don't act surprised when the manpage says so.

⭐ RETURN ⭐

0 on success, and a negative error code otherwise. that's it, that's the return vibe 🫶💖

cute sign-off time 🎀 this page comes from the libnvme API manual, dated October 2026, with footer source/version energy: libnvmf_insert_tls_key_velibnvmf_inse...ey_versioned(9). stay slay, bestie 💜🦋

📦 where this page comes from