CRYPTSETUP-CLOSE(8)

📦
version 2.8.8 · 17 versions
, in arch rolling, fedora 44, nixpkgs unstable

💖 CRYPTSETUP-CLOSE 💖

okay bestie, so this is cryptsetup-close — it lives in the Maintenance Commands part of the cryptsetup manual, section 8. And no cap, it does exactly one iconic thing: it closes stuff. Let's get into it 🫶

✨ NAME ✨

cryptsetup-close — removes the existing mapping <name> (and the associated key). bye girl 💅

🌸 SYNOPSIS 🌸

cryptsetup close [<options>] <name>

🦋 DESCRIPTION 🦋

So basically: it removes the existing mapping <name> and wipes the key from kernel memory. That's the whole vibe. Gone. Deleted. Not me crying over a wiped key 😭

For backward compatibility, there are a bunch of close command aliases, and they're all giving the same energy: remove, plainClose, luksClose, loopaesClose, tcryptClose, bitlkClose. They all behave the same, because the device type is determined automatically from the active device. iykyk ✨

<options> can be [--deferred, --cancel-deferred, --header, --disable-locks].

👑 OPTIONS 👑

  • --batch-mode, -q — Suppresses all confirmation questions. Use with care, bestie, fr fr! 🚨 And also: if the --verify-passphrase option is not specified, this option also switches off the passphrase verification.
  • --cancel-deferred — Removes a previously configured deferred device removal in the close command. Undoing the undoing, we love to see it 🎀
  • --debug or --debug-json — Run in debug mode with full diagnostic logs. Debug output lines are always prefixed by #. And if you use --debug-json, additional LUKS2 JSON data structures are printed. nerdy and gorgeous 💜
  • --deferred — Defers device removal in the close command until the last user closes it. It's giving "we'll leave when everyone's ready" 🌸
  • --disable-locks — Disable lock protection for metadata on disk. This option is valid only for LUKS2 and is ignored for other formats.
WARNING: Do not use this option unless you run cryptsetup in a restricted environment where locking is impossible to perform (where /run directory cannot be used). Like, seriously. Do not. 🙈
  • --header <device or file storing the LUKS header> — Use a detached (separated) metadata device or file where the LUKS header is stored. This option allows one to store the ciphertext and LUKS header on different devices. Separate but together, the main character couple energy 💖

For commands that change the LUKS header (e.g., luksAddKey), specify the device or file with the LUKS header directly as the LUKS device.

  • --help, -? — Show help text and default parameters. ✨
  • --usage — Show short option help.
  • --version, -V — Show the program version.

🍓 REPORTING BUGS 🍓

Report bugs at cryptsetup mailing list <cryptsetup@lists.linux.dev> or in Issues project section <https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>. slay, they're actually listening 🫶

Please attach the output of the failed command with --debug option added. That's the receipt, bestie, they need it 📝

🌈 SEE ALSO 🌈

Cryptsetup FAQ <https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions>

cryptsetup(8), integritysetup(8) and veritysetup(8) — the whole friend group 💜

⭐ CRYPTSETUP ⭐

Part of cryptsetup project <https://gitlab.com/cryptsetup/cryptsetup/>. iconic behavior, honestly 👑

and that's the whole page, bestie!! this one's cryptsetup 2.8.8, dated 2026-09-07, and it's part of the cryptsetup project at <https://gitlab.com/cryptsetup/cryptsetup/>. go close that mapping, you absolute legend 🦋💖 periodt.

📦 where this page comes from