libnvme(2)

✨ NAME ✨

okay bestie, so this is the API Manual for libnvme section 2, and today's main character is enum nvmf_tcp_sectype — it's literally the Transport Specific Address Subtype Definition for the NVMe/TCP Transport. no cap. 💅

---

🦋 SYNOPSIS 🦋

it's giving very much this, and nothing else:

enum nvmf_tcp_sectype {
    NVMF_TCP_SECTYPE_NONE ,
    NVMF_TCP_SECTYPE_TLS ,
    NVMF_TCP_SECTYPE_TLS13

};

like. that's the whole vibe. three little constants, zero drama. 🌸

---

🎀 Constants 🎀

NVMF_TCP_SECTYPE_NONE

No security. that's it, that's the girl. no TLS, no encryption, we're just rawdogging the network 🙈🔓

NVMF_TCP_SECTYPE_TLS

Transport Layer Security version 1.2. okay so it's TLS, but the older one, 1.2 specifically, periodt. 🔥

NVMF_TCP_SECTYPE_TLS13

Transport Layer Security version 1.3 or a subsequent version. (yes bestie, "or a subsequent version" — she's flexible like that 💅) the way that the TLS protocol negotiates the version and the cipher suite for each TCP connection is honestly iconic, every single connection gets its own little negotiation moment. main character energy fr fr. 👑

---

ngl, pick your constant wisely, because this is literally the security type of the transport and there is no undo button on a bad security choice 🫶

---

and that's the whole page, bestie!! 💖 this was enum nvmf_tcp_sectype from the libnvme API Manual (section 2), and the footer energy says July 2026 — dated and documented, slay. go forth and secure your TCP connections. ⭐🧚💜