Am 19.02.2012 00:11, schrieb Jan Engelhardt:
On Wednesday 2012-02-15 19:12, Michael Domann wrote:
Dec 25 08:09:54 sysiphus login[3411]: (mount.c:267): Mount info:
globalconf, user=mdomann<volume fstype="crypto_LUKS" server="(null)"
path="/dev/sda3" mountpoint="/home" cipher="(null)" fskeypath="(null)"
fskeycipher="(null)" fskeyhash="(null)" options="fsck" /> fstab=0 ssh=0
Dec 25 08:09:56 sysiphus login[3411]: (mount.c:586): ehd_keydec_run:
Unknown digest
What were the luksFormat commands/parameters you used to create this
volume?
If you do not remember, using luksDump can provide an approximation.
root@sysiphus:/home/mdomann# cryptsetup luksDump /dev/sdb2
LUKS header information for /dev/sdb2
Version: 1
Payload offset: 2056
Key Slot 0: ENABLED
Key Slot 1: ENABLED
Key Slot 2: ENABLED
Key Slot 3: ENABLED
Dec 25 08:09:56 sysiphus login[3411]: (pam_mount.c:602): going to readconfig
/home/mdomann/.pam_mount.conf.xml
Dec 25 08:09:56 sysiphus login[3411]: (mount.c:586): ehd_keydec_run: Unknown
digest
Dec 25 08:10:00 sysiphus login[3411]: (mount.c:695): error sending password to
mount
Dec 25 08:10:00 sysiphus kernel: login[3411]: segfault at 0 ip 00007fc0cdd7c359
sp 00007fff13cfb3b0 error 4 in libc-2.13.so[7fc0cdd05000+17a000]
The sda3 volume seems ok.
What is in /home/mdomann/.pam_mount.conf.xml?
The error happens after that is being parsed.
yes, the mount of sda3 is work as expected. the file
mdomann@sysiphus:~$ cat .pam_mount.conf.xml
<?xml version="1.0" encoding="utf-8" ?>
<pam_mount>
<debug enable="1" />
<!-- Volume definitions -->
<volume user="mdomann" fstype="crypto_LUKS" path="/dev/sdb2"
mountpoint="/home/mdomann/media" fskeypath="/home/mdomann/.gnupg/media"
fskeyhash="none" fskeycipher="none"
options="fsck,nodev,nosuid" />
</pam_mount>
mdomann@sysiphus:~$
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
