NVME-CHECK-DHCHAP-KEY(1)

📦 version 3.2, in arch rolling

💅 nvme-check-dhchap-key — the manual page, bestie edition ✨

okay so real talk: this is the nvme-check-dhchap-key page from the NVME-CHECK-DHCHAP(1) manual, and honestly? It's giving "legacy era, we don't really do that anymore" energy. But we're gonna read it together anyway because you deserve to know. 🫶

🌸 NAME 🌸

nvme-check-dhchap-key — check a host DH-HMAC-CHAP secret. Oh, and it's deprecated. Yeah. I know. 😭

🦋 SYNOPSIS 🦋

nvme [<global-options>] check-dhchap-key [--key=<secret> | -k <secret>]

that's it. that's the whole vibe. one option. iconic minimalism honestly.

💖 DESCRIPTION 💖

So here's the tea ☕: this command is a deprecated alias for nvme-keys-check-kxchap-secret(1). It exists purely so your old scripts — the ones written against nvme-cli versions older than 3.0 — don't just break down crying. Respectful, honestly. 🫶

It takes exactly one option, --key/-k, which is the same one nvme-cli 2.x took, and it passes that secret straight through to that other command. Simple. Lowkey elegant.

Exit codes still match 2.x, no cap. BUT — and this is the part where you need to pay attention, bestie 👀 — the messages changed:

  • Key is valid, Key is loaded and Key is not loaded are now Secret is ...
  • the validation errors say secret where they used to say key
⚠️ so if your script is out here matching on the old wording? It needs updating. fr fr. Do not skip this. 💀

Now, about --keydata, --keyring, --keytype and --identity — those exist, but they're only reachable under nvme keys check-kxchap-secret. Not here. Not your moment, queen. 🙈

And if you run this with no --key? The secret gets read from stdin — which is a change, because 2.x would just report Key not specified at you. Glow-up behavior, honestly. ✨

🚨 New scripts should use nvme keys check-kxchap-secret instead. Periodt. This alias prints a deprecation warning on stderr and may be removed in a future release. It's giving "I have main character energy but my time is coming to an end." 💅

For the full option reference, go see nvme-keys-check-kxchap-secret(1). That's where the real feast is. 🍓

✨ GLOBAL OPTIONS ✨

These are the top-level nvme command options, and they're all available to this subcommand too. Group chat rules: everybody eats. 💜

  • --dry-run — prints the command that would be executed, but doesn't actually run it. Manifesting the command without the consequences, honestly. 🧚
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support. bye bye, probing. 👋
  • --no-retries — disables the retry logic on transient errors. One shot, no second chances. 💀
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, 'json, or binary. Only one output format may be used at a time, so pick your fighter. 👑
  • --output-format-version=<version> — selects the output format version. Version 1 uses the original field naming, while version 2 (the default) gives you more consistent and script-friendly field names. Any other version? Rejected. 🚫
  • --quiet — suppresses informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. silence is a vibe. 🤫
  • --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation. The supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. Four little keys, four little doors. 🎀
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). patience is a virtue, apparently. ⭐
  • -v, --verbose — increases the level of detail in the output. You can specify it multiple times to crank the verbosity even further. go off, be nosy. 🔥

and yes — these can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file, though. CLI stays the main character. 💅

🌈 EXAMPLES 🌈

No Examples

that's it. that's the section. she said "no thoughts, head empty." 😭✨

🎀 NVME 🎀

Part of the nvme-user suite. one big happy family. 🫶

🌸 SEE ALSO 🌸

okay that's the whole page!! 💖 every last flag, every path, every caveat — all present and accounted for, no cap. this is nvme-check-dhchap-key from the NVME-CHECK-DHCHAP(1) manual, part of the nvme-user suite, and that's your sign-off, so go update those scripts. iykyk. 🎀✨💅

📦 where this page comes from