FM / scripts

/snap/core24/1643/usr/lib/cryptsetup/scripts/

/snap/core24/1643/usr/lib/cryptsetup/scripts

Name	Size	Mode	Actions
decrypt_derived	1106	0755	edit dl rm
decrypt_gnupg	570	0755	edit dl rm
decrypt_gnupg-sc	953	0755	edit dl rm
decrypt_keyctl	2042	0755	edit dl rm
decrypt_opensc	1396	0755	edit dl rm
decrypt_ssl	347	0755	edit dl rm
passdev	14648	0755	edit dl rm

Edit: /snap/core24/1643/usr/lib/cryptsetup/scripts/decrypt_opensc (1396B)

#!/bin/sh

# Why not use "openct-tool rwait" instead of polling opensc-tool exit status?
# Well openct daemon has to be running which interferes with pcscd since both
# implement reader drivers, my particular CCID reader (SCM SCR331-LC1) doesn't
# work with the CCID driver in openct, however it does work with pcscd.

# Why not use "opensc-tool --wait" instead of polling opensc-tool exit status?
# Although opensc-tool --help reports that there is a --wait option, it doesn't
# seem to be implemented.

check_card() {
    cardfound=0

if /usr/bin/opensc-tool -n >/dev/null 2>&1; then
        cardfound=1
    fi
}

wait_card() {
    check_card
    if [ $cardfound = 0 ] ; then
        echo "Waiting for Smart Card..." >&2
        tries=0
        while [ $cardfound = 0 ] && [ $tries -lt 60 ] ; do
            sleep 1
            check_card
            tries=$(($tries + 1))
        done
        if [ $cardfound = 0 ] ; then
            echo 'Failed to find Smart Card card!' >&2
            exit 1
        fi
    fi
}

wait_card
if [ -x /bin/plymouth ] && plymouth --ping; then
	# Get pin number from plymouth
	/usr/bin/pkcs15-crypt --decipher --input "$1" --pkcs1 --raw \
		--pin "$(plymouth ask-for-password --prompt "Enter pin for $CRYPTTAB_NAME: ")"
else
	# Get pin number from console
	/usr/bin/pkcs15-crypt --decipher --input "$1" --pkcs1 --raw </dev/console 2>/dev/console
fi
exit $?

cmd: