nvme_auth_derive_tls_psk(9)

🎀 nvme_auth_derive_tls_psk(9) — Kernel API Manual 🎀

okay so bestie, this page is from the Kernel API Manual, and the icon is nvme_auth_derive_tls_psk — she’s literally here to Derive TLS PSK. crypto girl summer, no cap. 💅✨

🌸 NAME 🌸

• nvme_auth_derive_tls_psk — Derive TLS PSK

✨ SYNOPSIS ✨

int nvme_auth_derive_tls_psk (int hmac_id , const u8 *psk , size_t
       psk_len , const char *psk_digest , u8 **ret_psk );

🫶 ARGUMENTS 🫶

• hmac_id — Hash function identifier. like, which hash function we’re using, bestie.
• psk — generated input PSK. yep, that’s the PSK going in.
• psk_len — size of psk. literally how big the psk is.
• psk_digest — TLS PSK digest. the digest, periodt.
• ret_psk — Pointer to the resulting TLS PSK. where the resulting TLS PSK pointer lands.

🧚 DESCRIPTION 🧚

okay so here’s the tea: you derive a TLS PSK as specified in TP8018 Section 3.6.1.3: TLS PSK and PSK identity Derivation.

The TLS PSK shall be derived as follows from an input PSK (i.e., either a retained PSK or a generated PSK) and a PSK identity using the HKDF-Extract and HKDF-Expand-Label operations (refer to RFC 5869 and RFC 8446), where the hash function is the one specified by the hash specifier of the PSK identity:

1. PRK = HKDF-Extract(0, Input PSK); and
2. TLS PSK = HKDF-Expand-Label(PRK, "nvme-tls-psk", PskIdentityContext, L), where PskIdentityContext is the hash identifier indicated in the PSK identity concatenated to a space character and to the Base64 PSK digest (i.e., "<hash> <PSK digest>") and L is the output size in bytes of the hash function (i.e., 32 for SHA-256 and 48 for SHA-384).

She returns 0 on success with a valid psk pointer in ret_psk, or a negative error number otherwise. that’s the whole vibe check. 💖

🔗 SEE ALSO 🔗

• Kernel file ./drivers/nvme/common/auth.c
• nvme_auth_augmented_challenge(9)
• nvme_auth_gen_session_key(9)
• nvme_auth_generate_psk(9)
• nvme_auth_generate_digest(9)

okay bye bestie 💖 source/version: ./drivers/nvme/common; date: October 2026 🫶