SWAMPy

✎ CARVE FLESH

EDITING: decrypt_derived

#!/bin/sh

# WARNING: If you use the decrypt_derived keyscript for devices with
# persistent data (i.e. not swap or temp devices), then you will lose
# access to that data permanently if something damages the LUKS header
# of the LUKS device you derive from. The same applies if you luksFormat
# the device, even if you use the same passphrase(s). A LUKS header
# backup, or better a backup of the data on the derived device may be
# a good idea. See the Cryptsetup FAQ on how to do this right.

if [ -z "$1" ]; then
    echo "$0: must be executed with a crypto device as argument" >&2
    exit 1
fi

unset -v keys count
keys="$(dmsetup table --target crypt --showkeys -- "$1" 2>/dev/null | cut -s -d' ' -f5)"
count="$(printf '%s' "$keys" | wc -l)"

if [ -n "$keys" ] && [ $count -le 1 ]; then
    if [ "${keys#:}" = "$keys" ]; then
        printf '%s' "$keys" | tr -d '\n'
    else
        echo "$0: device $1 uses the kernel keyring"
    fi
elif [ $count -eq 0 ]; then
    echo "$0: device $1 doesn't exist or isn't a crypto device" >&2
else
    echo "$0: more than one device match" >&2
fi
exit 1

CANCEL

Name	Type	Size	Modified	Actions
↩ ..	DIR	—	—
📄 decrypt_derived	?	1.1 KB	2020-02-04 13:11	EDIT
📄 decrypt_gnupg	?	570 B	2020-02-04 13:11	EDIT
📄 decrypt_gnupg-sc	?	953 B	2020-02-04 13:11	EDIT
📄 decrypt_keyctl	?	2 KB	2020-02-04 13:11	EDIT
📄 decrypt_opensc	?	1.4 KB	2020-02-04 13:11	EDIT
📄 decrypt_ssl	?	347 B	2020-02-04 13:11	EDIT
📄 passdev	?	14.3 KB	2025-01-29 18:37	EDIT