diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-29 04:41:05 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-29 04:41:05 +0000 |
commit | 1cc8413aaf5f8fa6595aece1933462c096e88639 (patch) | |
tree | e97b4f25c511372d73bdd96c389c5f468d99138a /Documentation/nvme-security-send.txt | |
parent | Initial commit. (diff) | |
download | nvme-cli-upstream.tar.xz nvme-cli-upstream.zip |
Adding upstream version 2.4+really2.3.upstream/2.4+really2.3upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'Documentation/nvme-security-send.txt')
-rw-r--r-- | Documentation/nvme-security-send.txt | 72 |
1 files changed, 72 insertions, 0 deletions
diff --git a/Documentation/nvme-security-send.txt b/Documentation/nvme-security-send.txt new file mode 100644 index 0000000..ae22628 --- /dev/null +++ b/Documentation/nvme-security-send.txt @@ -0,0 +1,72 @@ +nvme-security-send(1) +===================== + +NAME +---- +nvme-security-send - Security Send command + +SYNOPSIS +-------- +[verse] +'nvme security-send' <device> [--file=<file> | -f <file>] + [--secp=<security-protocol> | -p <security-protocol>] + [--spsp=<protocol-specific> | -s <protocol-specific>] + [--tl=<transfer-length> | -t <transfer-length>] + [--nssf=<nvme-specific> | -N <nvme-specific>] + [--namespace-id=<nsid> | -n <nsid>] + +DESCRIPTION +----------- +The Security Send command is used to transfer security protocol data +to the controller. The data structure transferred to the controller +as part of this command contains security protocol specific commands +to be performed by the controller. The data structure transferred may +also contain data or parameters associated with the security protocol +commands. Status and data that is to be returned to the host for the +security protocol commands submitted by a Security Send command are +retrieved with the Security Receive command. + +The association between a Security Send command and subsequent Security +Receive command is Security Protocol field dependent as defined in SPC-4. + +OPTIONS +------- +-n <nsid>:: +--namespace-id=<nsid>:: + Target a specific namespace for this security command. + +-N <nssf>:: +--nssf=<nssf>:: + NVMe Security Specific field. If using security protocol EAh + assigned for NVMe use, the NVMe security specific field indicates + which reply memory buffer target. + +-f <file>:: +--file=<file>:: + Path to file used as the security protocol's payload. Required + argument. + +-p <security-protocol>:: +--secp=<security-protocol>:: + Security Protocol: This field specifies the security protocol + as defined in SPC-4. The controller shall fail the command with + Invalid Parameter indicated if a reserved value of the Security + Protocol is specified. + +-s <security-protocol-specific>:: +--spsp=<security-protocol-specific>:: + SP Specific: The value of this field is specific to the Security + Protocol as defined in SPC-4. + +-t <trans-length>:: +--tl=<trans-length>:: + Transfer Length: The value of this field is specific to the + Security Protocol as defined in SPC-4. + +EXAMPLES +-------- +No Examples + +NVME +---- +Part of the nvme-user suite |