[Bug 353935] Re: mount.crypt segfaults when switching to battery

[jhansonxi]

I'm encountering this on a new Jaunty server I set up so it's not a
battery-related issue.  I have an encrypted LVM volume that is supposed
to mount the user's home directory via pam_mount.  I enter the password
and get a command prompt but the mount fails.  Kernel reports:

[ 1148.939559] mount.crypt[3796]: segfault at fffffffffffffffc ip 00007f82c5da0cfd sp 00007fffce1c4a70 error 4 in libHX.so.14.2.0[7f82c5d9b000+b000]
[ 1149.635703] mount.crypt[3802]: segfault at fffffffffffffffc ip 00007fae4424ecfd sp 00007fff4c672f30 error 4 in libHX.so.14.2.0[7fae44249000+b000]

This occurs at every login and logout.  The pam_mount config section is:

     <volume user="wineuser"
	fstype="crypt"
	path="/dev/mapper/vg0-lv4"
        mountpoint="/home/wineuser"
        options="defaults,fsck"
	fskeycipher="aes-256-ecb"
        fskeypath="/etc/keys/dm-crypt/wineuser_crypt.key"
    />


Manually mounting it via mount.crypt works:

root at jhansonxi-s2:/home/administrator/Install# cat mount.crypt.sh
#! /bin/sh
mount.crypt -v -o keyfile="/etc/keys/dm-crypt/wineuser_crypt.key",fsk_cipher="aes-256-ecb",fsk_hash="md5" /dev/mapper/vg0-lv4 /home/wineuser
root at jhansonxi-s2:/home/administrator/Install# ./mount.crypt.sh
command: [readlink] [-fn] [/dev/mapper/vg0-lv4] 
command: [readlink] [-fn] [/home/wineuser] 
Password: 
mount.crypt(loop.c:319): Using _dev_mapper_vg0_lv4 as dmdevice name
command: [cryptsetup] [luksOpen] [/dev/mapper/vg0-lv4] [_dev_mapper_vg0_lv4] 
key slot 0 unlocked.
Command successful.
command: [mount] [-n] [/dev/mapper/_dev_mapper_vg0_lv4] [/home/wineuser] 
root at jhansonxi-s2:/home/administrator/Install# umount.crypt /home/wineuser
root at jhansonxi-s2:/home/administrator/Install#

** Attachment added: "Serial console capture of login with pam_mount debug mode"
   http://launchpadlibrarian.net/26646539/mount.crypt_pam_mount_debug.txt

-- 
mount.crypt segfaults when switching to battery
https://bugs.launchpad.net/bugs/353935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs