LIBNVMF_GENERATE_TLS_KEY_IDENTITY_COMPAT-LIBNVME3(2)

📦 version 3.2, in arch rolling

🎀 NAME 🎀

okay so bestie, meet libnvmf_generate_tls_key_identity_compat from the libnvme API manual — it's the one that generates the TLS PSK identity. literally what it says on the tin 💅

✨ SYNOPSIS ✨

int libnvmf_generate_tls_key_identity_compat (struct libnvme_global_ctx
*ctx , const char *hostnqn , const char *subsysnqn , int version , enum
libnvmf_hmac_alg hmac , unsigned char *configured_key , int key_len ,
char **identity );

🫶 ARGUMENTS 🫶

  • ctx — a struct libnvme_global_ctx object, aka the global context bestie 🫶
  • hostnqn — Host NVMe Qualified Name ✨
  • subsysnqn — Subsystem NVMe Qualified Name 🌸
  • version — TLS PSK identity version to use 👑
  • hmac — HMAC algorithm 🔥
  • configured_key — Configured PSK to derive the retained PSK from 🎀
  • key_len — Length of configured_key 🦋
  • identity — TLS PSK identity to return 💖

🦋 DESCRIPTION 🦋

so basically it derives a retained PSK as specified in the NVMe TCP Transport Specification 1.3, section 3.6.1.3, and generates the corresponding TLS PSK identity. no cap ✨

this one is the compat girlie, and it differs from libnvmf_generate_tls_key_identity in that it uses the original implementation for HKDF-Expand-Label which does not prefix the 'info' and 'label' strings with the length. iykyk 💅

it's giving “you own this memory now” 💀 — it is the responsibility of the caller to free the returned string.

💖 RETURN 💖

  • 0 on success, negative error code otherwise. periodt 🌈

mwah 💋 — that's the tea from the libnvme API manual, October 2026, libnvmf_generate_tls_key_identity_compat(9). bestie, you got this 🫶✨

📦 where this page comes from