| 1 |
.TH "nvme_scan_tls_keys" 9 "nvme_scan_tls_keys" "November 2025" "libnvme API manual" LINUX |
| 2 |
.SH NAME |
| 3 |
nvme_scan_tls_keys \- Iterate over TLS keys in a keyring |
| 4 |
.SH SYNOPSIS |
| 5 |
.B "int" nvme_scan_tls_keys |
| 6 |
.BI "(const char *keyring " "," |
| 7 |
.BI "nvme_scan_tls_keys_cb_t cb " "," |
| 8 |
.BI "void *data " ");" |
| 9 |
.SH ARGUMENTS |
| 10 |
.IP "keyring" 12 |
| 11 |
Keyring holding TLS keys |
| 12 |
.IP "cb" 12 |
| 13 |
Callback function |
| 14 |
.IP "data" 12 |
| 15 |
Pointer for data to be passed to \fIcb\fP |
| 16 |
.SH "DESCRIPTION" |
| 17 |
Iterates \fIkeyring\fP and call \fIcb\fP for each TLS key. When \fIkeyring\fP is NULL |
| 18 |
the default '.nvme' keyring is used. |
| 19 |
A TLS key must be of type 'psk' and the description must be of the |
| 20 |
form 'NVMe<0|1><R|G>0<1|2> <identity>', otherwise it will be skipped |
| 21 |
during iteration. |
| 22 |
.SH "RETURN" |
| 23 |
Number of keys for which \fIcb\fP was called, or -1 with errno set |
| 24 |
on error. |