Scroll to navigation

NVME-KEYS-REVOKE(1) NVMe Manual NVME-KEYS-REVOKE(1)

NAME

nvme-keys-revoke - Revoke a NVMe TLS PSK from a keyring

SYNOPSIS

nvme [<global-options>] keys revoke [--keyring=<name> | -k <name>]


                        [--keytype=<type> | -t <type>]


                        --identity=<description> | -i <description>

DESCRIPTION

Revoke an NVMe TLS pre-shared key (PSK) from the system keyring.

OPTIONS

-k <name>, --keyring=<name>

Name of the keyring to revoke the key from. Default is .nvme.

-t <type>, --keytype=<type>

Type of the key to revoke. Default is psk.

-i <description>, --identity=<description>

Identity (description) of the key to revoke.

GLOBAL OPTIONS

The following options are defined at the top-level nvme command and are available to this subcommand:

--dry-run

Print the command that would be executed, but do not actually execute it.

--no-ioctl-probing

Disable probing for 64-bit IOCTL support.

--no-retries

Disable retry logic on transient errors.

-o <fmt>, --output-format=<fmt>

Set the reporting format to normal, tabular, 'json, or binary. Only one output format may be used at a time.

--output-format-version=<version>

Select the output format version. Version 1 uses the original field naming, while version 2 (default) provides more consistent and script-friendly field names.

--timeout=<ms>

Set the timeout for the command in milliseconds.

-v, --verbose

Increase the level of detail in the output. May be specified multiple times to further increase verbosity.

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file.

EXAMPLES

•Revoke a key using its description and verify with keyctl 

# nvme keys revoke --identity="NVMe0R01 hostnqn0 subsys0"
# keyctl show
Session Keyring


 573249525 --alswrv      0     0  keyring: _ses


 353599402 --alswrv      0 65534   \_ keyring: _uid.0


 475911922 ---lswrv      0     0   \_ keyring: .nvme
649274894: key inaccessible (Key has been revoked)

NVME

Part of the nvme-user suite

09/19/2026 NVMe