Debian Codegraph @

doc/man/nvme_generate_tls_key_identity_compat.2

raw
1 .TH "nvme_generate_tls_key_identity_compat" 9 "nvme_generate_tls_key_identity_compat" "November 2025" "libnvme API manual" LINUX
2 .SH NAME
3 nvme_generate_tls_key_identity_compat \- Generate the TLS key identity
4 .SH SYNOPSIS
5 .B "char *" nvme_generate_tls_key_identity_compat
6 .BI "(const char *hostnqn " ","
7 .BI "const char *subsysnqn " ","
8 .BI "int version " ","
9 .BI "int hmac " ","
10 .BI "unsigned char *configured_key " ","
11 .BI "int key_len " ");"
12 .SH ARGUMENTS
13 .IP "hostnqn" 12
14 Host NVMe Qualified Name
15 .IP "subsysnqn" 12
16 Subsystem NVMe Qualified Name
17 .IP "version" 12
18 Key version to use
19 .IP "hmac" 12
20 HMAC algorithm
21 .IP "configured_key" 12
22 Configured key data to derive the key from
23 .IP "key_len" 12
24 Length of \fIconfigured_key\fP
25 .SH "DESCRIPTION"
26 Derives a 'retained' TLS key as specified in NVMe TCP and
27 generate the corresponding TLs identity. This version differs
28 from \fI\fP\fBnvme_generate_tls_key_identity\fP in that it uses the original
29 implementation for HKDF-Expand-Label which does not prefix the 'info'
30 and 'label' string with the length.
31 .SH "RETURN"
32 The string containing the TLS identity. It is the responsibility
33 of the caller to free the returned string.