From 3040652984f5b967d7fda2c4f7f6690bcedc8857 Mon Sep 17 00:00:00 2001
From: moparisthebest <admin@moparisthebest.com>
Date: Thu, 24 Nov 2016 00:31:25 -0500
Subject: [PATCH] Add readme and encrypt_install

---
 encrypt_install | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
 readme.md       |  5 +++++
 2 files changed, 54 insertions(+)
 create mode 100644 encrypt_install
 create mode 100644 readme.md

diff --git a/encrypt_install b/encrypt_install
new file mode 100644
index 0000000..9ebf342
--- /dev/null
+++ b/encrypt_install
@@ -0,0 +1,49 @@
+#!/bin/bash
+
+build() {
+    local mod
+
+    add_module dm-crypt
+    if [[ $CRYPTO_MODULES ]]; then
+        for mod in $CRYPTO_MODULES; do
+            add_module "$mod"
+        done
+    else
+        add_all_modules '/crypto/'
+    fi
+
+    add_binary "cryptsetup"
+    add_binary "dmsetup"
+    add_file "/usr/lib/udev/rules.d/10-dm.rules"
+    add_file "/usr/lib/udev/rules.d/13-dm-disk.rules"
+    add_file "/usr/lib/udev/rules.d/95-dm-notify.rules"
+    add_file "/usr/lib/initcpio/udev/11-dm-initramfs.rules" "/usr/lib/udev/rules.d/11-dm-initramfs.rules"
+
+    add_runscript
+}
+
+help() {
+    cat <<HELPEOF
+This hook allows for multiple encrypted root devices. Users should specify the
+device to be unlocked using 'cryptdevice=device:dmname' on the kernel command
+line, where 'device' is the path to the raw device, and 'dmname' is the name 
+given to the device after unlocking, and will be available as /dev/mapper/dmname.
+
+Subsequent devices must be specified the same way, but with cryptdevice1=,
+cryptdevice2= and so on, in order. Passwords will be cached and attempted to
+re-use them on the next device, and if that fails, a new password will be asked
+for.
+
+For unlocking via keyfile, 'cryptkey=device:fstype:path' should be specified on
+the kernel cmdline, where 'device' represents the raw block device where the key
+exists, 'fstype' is the filesystem type of 'device' (or auto), and 'path' is
+the absolute path of the keyfile within the device.
+
+Without specifying a keyfile, you will be prompted for the password at runtime.
+This means you must have a keyboard available to input it, and you may need
+the keymap hook as well to ensure that the keyboard is using the layout you
+expect.
+HELPEOF
+}
+
+# vim: set ft=sh ts=4 sw=4 et:
diff --git a/readme.md b/readme.md
new file mode 100644
index 0000000..016a699
--- /dev/null
+++ b/readme.md
@@ -0,0 +1,5 @@
+This is the standard archlinux encrypt hook extended to support multiple encrypted devices via cryptsetup= cryptsetup1= cryptsetup2= etc.
+
+Hopefully one day it will be merged with the normal archlinux cryptsetup package (ask for it [here](https://bugs.archlinux.org/task/23182)), until then it will be available via the aur here:
+
+https://aur.archlinux.org/packages/cryptsetup-multidisk/