Hi,
I upgraded to Hardy from Gutsy Gibbon and now I cannot execute files in my home directory anymore. It appears that my encrypted home directory is mounted with "noexec" option even though I specified otherwise (and it worked before the upgrade).
I had used the following tutorial to encrypt my home directory: http://www.felipe-alfaro.org/blog/20...ng-cryptoloop/
This is what mount tells me:
aiwa@magnolia:~$ mount
/dev/sda6 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.24-16-generic/volatile type tmpfs (rw)
/dev/sda2 on /boot type ext2 (rw)
securityfs on /sys/kernel/security type securityfs (rw)
/home/aiwa.img on /home/aiwa type ext3 (rw,noexec,nosuid,nodev,loop=/dev/loop1,encryption=aes,keybits=256)
gvfs-fuse-daemon on /home/aiwa/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=aiwa)
Here's the line in pam_mount.conf.xml that mounts my home directory on login:
<volume fskeycipher="aes-256-ecb" options="loop,user,exec,encryption=aes,keybits=256 " fskeypath="/home/aiwa.key" user="aiwa" mountpoint="/home/aiwa" path="/home/aiwa.img" fstype="ext3" />
This is really baffling me. Is this a bug in the new pam release, or the result of some new security policy hidden in another configuration file? Your input is appreciated
I upgraded to Hardy from Gutsy Gibbon and now I cannot execute files in my home directory anymore. It appears that my encrypted home directory is mounted with "noexec" option even though I specified otherwise (and it worked before the upgrade).
I had used the following tutorial to encrypt my home directory: http://www.felipe-alfaro.org/blog/20...ng-cryptoloop/
This is what mount tells me:
aiwa@magnolia:~$ mount
/dev/sda6 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.24-16-generic/volatile type tmpfs (rw)
/dev/sda2 on /boot type ext2 (rw)
securityfs on /sys/kernel/security type securityfs (rw)
/home/aiwa.img on /home/aiwa type ext3 (rw,noexec,nosuid,nodev,loop=/dev/loop1,encryption=aes,keybits=256)
gvfs-fuse-daemon on /home/aiwa/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=aiwa)
Here's the line in pam_mount.conf.xml that mounts my home directory on login:
<volume fskeycipher="aes-256-ecb" options="loop,user,exec,encryption=aes,keybits=256 " fskeypath="/home/aiwa.key" user="aiwa" mountpoint="/home/aiwa" path="/home/aiwa.img" fstype="ext3" />
This is really baffling me. Is this a bug in the new pam release, or the result of some new security policy hidden in another configuration file? Your input is appreciated
Comment