nvme/nvme-cli
1
0
Fork 0
Code Issues Activity

Adding upstream version 2.11.

Browse source 
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-02-16 12:28:14 +01:00
parent 6f96c7c854
commit 65508f0a28
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
533 changed files with 9033 additions and 4835 deletions
Download patch file Download diff file Expand all files Collapse all files

24
Documentation/nvme-connect.1
View file

@ -2,12 +2,12 @@
.\" Title: nvme-connect
.\" Author: [see the "AUTHORS" section]
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
.\" Date: 08/05/2024
.\" Date: 10/31/2024
.\" Manual: NVMe Manual
.\" Source: NVMe
.\" Language: English
.\"
.TH "NVME\-CONNECT" "1" "08/05/2024" "NVMe" "NVMe Manual"
.TH "NVME\-CONNECT" "1" "10/31/2024" "NVMe" "NVMe Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@ -50,7 +50,8 @@ nvme-connect \- Connect to a Fabrics controller\&.
[\-\-keep\-alive\-tmo=<#> | \-k <#>]
[\-\-reconnect\-delay=<#> | \-c <#>]
[\-\-ctrl\-loss\-tmo=<#> | \-l <#>] [\-\-tos=<#> | \-T <#>]
[\-\-keyring=<#>] [\-\-tls_key=<#>]
[\-\-keyring=<keyring>] [\-\-tls\-key=<tls\-key>]
[\-\-tls\-key\-identity=<identity>]
[\-\-duplicate\-connect | \-D] [\-\-disable\-sqflow ]
[\-\-hdr\-digest | \-g] [\-\-data\-digest | \-G] [\-\-tls]
[\-\-concat] [\-\-dump\-config | \-O] [\-\-application=<id>]
@ -198,14 +199,23 @@ seconds\&.
Type of service for the connection (TCP)
.RE
.PP
\-\-keyring=<#>
\-\-keyring=<keyring>
.RS 4
Keyring for TLS key lookup\&.
Keyring for TLS key lookup, either the key id or the keyring name\&.
.RE
.PP
\-\-tls_key=<#>
\-\-tls\-key=<tls\-key>
.RS 4
TLS key for the connection (TCP)\&.
TLS key for the connection (TCP), either the TLS key in interchange format or the key id\&. It\(cqs strongly recommended not to provide the TLS key via the comamnd line due to security concerns\&. Instead in production situation, the key should be loaded into the keystore with
\fInvme tls \-\-import\fR
and only the
\fI\-\-tls\fR
options used\&. The kernel will select the matching key\&.
.RE
.PP
\-\-tls\-key\-identity=<identity>
.RS 4
The identity used for the tls\-key\&. If none is provided the tls\-key provided via the comamnd line is considered a configuration key and a derive key will be loaded into the keyring\&.
.RE
.PP
\-D, \-\-duplicate\-connect