Debian Codegraph @

doc/man/nvme_insert_tls_key_compat.2

raw
1 .TH "nvme_insert_tls_key_compat" 9 "nvme_insert_tls_key_compat" "November 2025" "libnvme API manual" LINUX
2 .SH NAME
3 nvme_insert_tls_key_compat \- Derive and insert TLS key
4 .SH SYNOPSIS
5 .B "long" nvme_insert_tls_key_compat
6 .BI "(const char *keyring " ","
7 .BI "const char *key_type " ","
8 .BI "const char *hostnqn " ","
9 .BI "const char *subsysnqn " ","
10 .BI "int version " ","
11 .BI "int hmac " ","
12 .BI "unsigned char *configured_key " ","
13 .BI "int key_len " ");"
14 .SH ARGUMENTS
15 .IP "keyring" 12
16 Keyring to use
17 .IP "key_type" 12
18 Type of the resulting key
19 .IP "hostnqn" 12
20 Host NVMe Qualified Name
21 .IP "subsysnqn" 12
22 Subsystem NVMe Qualified Name
23 .IP "version" 12
24 Key version to use
25 .IP "hmac" 12
26 HMAC algorithm
27 .IP "configured_key" 12
28 Configured key data to derive the key from
29 .IP "key_len" 12
30 Length of \fIconfigured_key\fP
31 .SH "DESCRIPTION"
32 Derives a 'retained' TLS key as specified in NVMe TCP 1.0a (if
33 \fIversion\fP s set to '0') or NVMe TP8028 (if \fIversion\fP is set to '1) and
34 stores it as type \fIkey_type\fP in the keyring specified by \fIkeyring\fP.
35 This version differs from \fI\fP\fBnvme_insert_tls_key_versioned\fP in that it
36 uses the original implementation for HKDF Expand-Label which does not
37 prefix the 'info' and 'label' strings with the length.
38 .SH "RETURN"
39 The key serial number if the key could be inserted into
40 the keyring or 0 with errno otherwise.