libnvmf_scan_tls_keys(9)

💅 libnvmf_scan_tls_keys

okay so bestie, welcome to the libnvme API manual — this little page is all about libnvmf_scan_tls_keys(9), and honestly? it's a vibe. ✨

🎀 NAME

libnvmf_scan_tls_keys — iterate over TLS PSKs in a keyring 🦋

✨ SYNOPSIS

int libnvmf_scan_tls_keys (struct libnvme_global_ctx *ctx , const char
*keyring , libnvmf_scan_tls_keys_cb_t cb , void *data );

🌸 ARGUMENTS

• ctx — your struct libnvme_global_ctx object, the main character of this whole operation tbh 👑
• keyring — the keyring that's holding all those TLS PSKs, like the little purse where the secrets live 👜
• cb — the callback function, aka the thing that gets called for each one, no cap
• data — a pointer for data that gets passed along to cb, lowkey just a little care package 🎁

💖 DESCRIPTION

So here's the tea: it iterates over keyring and calls cb for each TLS PSK it finds. Fr fr, that's the whole gig. 🫶

When keyring is NULL, the default '.nvme' keyring is used — iconic default behavior, we love to see it. 💅

Now, plot twist 🙈: a key that's holding a TLS PSK must be of type 'psk', and its description must be of the form 'NVMe<0|1><R|G><01|02> <identity>'. If it's not giving that exact energy, it gets skipped during iteration. Periodt. ⭐

ngl bestie, if your key isn't shaped like 'psk' with that 'NVMe<0|1><R|G><01|02> <identity>' description, it's literally not coming to the party — skipped, done, bye. 💀

🔥 RETURN

It returns the number of keys for which cb was called — or a negative error code if things went sideways 😭

---

and that's the whole page, bestie! 🌈 this gem is from the libnvmf_scan_tls_keys era, October 2026 — the same name up top and in the footer, which is honestly giving symmetry slay. go forth and scan those keys! 🍓🧚💜