From 78a8de758ed7f79fc7a37ecb12ec128c9763e4b7 Mon Sep 17 00:00:00 2001
From: Lena <126529524+acuteenvy@users.noreply.github.com>
Date: Sat, 7 Dec 2024 23:34:30 +0100
Subject: [PATCH] systemd-cryptsetup: add page (#15064)

---
 pages/linux/systemd-cryptsetup.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 pages/linux/systemd-cryptsetup.md

diff --git a/pages/linux/systemd-cryptsetup.md b/pages/linux/systemd-cryptsetup.md
new file mode 100644
index 0000000000..40f67d3bf1
--- /dev/null
+++ b/pages/linux/systemd-cryptsetup.md
@@ -0,0 +1,22 @@
+# systemd-cryptsetup
+
+> Create or remove decrypted mappings of encrypted volumes. Equivalent of `cryptsetup open` and `cryptsetup close`.
+> Arguments to this command are written exactly like a line in `/etc/crypttab`. It's used by systemd to unlock devices on boot.
+> See also: `cryptsetup`.
+> More information: <https://www.freedesktop.org/software/systemd/man/latest/systemd-cryptsetup.html>.
+
+- Open a LUKS volume and create a decrypted mapping at `/dev/mapper/mapping_name`:
+
+`systemd-cryptsetup attach {{mapping_name}} {{/dev/sdXY}}`
+
+- Open a LUKS volume with additional options and create a decrypted mapping at `/dev/mapper/mapping_name`:
+
+`systemd-cryptsetup attach {{mapping_name}} {{/dev/sdXY}} none {{crypttab_options}}`
+
+- Open a LUKS volume with a keyfile and create a decrypted mapping at `/dev/mapper/mapping_name`:
+
+`systemd-cryptsetup attach {{mapping_name}} {{/dev/sdXY}} {{path/to/keyfile}} {{crypttab_options}}`
+
+- Remove an existing mapping:
+
+`systemd-cryptsetup detach {{mapping_name}}`