Michael Halcrow wrote the following on 09/06/2007 08:23 PM:
On Thu, Sep 06, 2007 at 08:08:32PM +0200, Stefan Farestam wrote:
Ok. Any guess as to what I need to change /update in my distro to
get this working? I use a stock kernel from kernel.org instead of
the one supplied by Ubuntu.
I don't think anything that drastic is going to be necessary. The
kernel you are using does not matter. What matters is what /bin/mount
is adding to the -o option set when you perform the mount. It's going
to take some detective work to find out why /bin/mount is setting the
noexec flag in your particular case; maybe it's something in your
/etc/fstab, or maybe it has something to do with your flags set on
your lower mount.
Interesting. Your comments prompted me to try around a bit with mount
options and I discovered that if I mount the encrypted file system
explicitly the noexec file is not set but when I use "mount -i" it is set.
This works fine (mounts the file system and noexec flag is not set in
/etc/mtab):
mount -t ecryptfs /b/encrypted /b/protected -o
cipher=aes,ecryptfs_key_bytes=32
This does not work (mounts the file system ok but yields the noexec flag
in /etc/mtab):
mount -i
What could be going on here?
--
Stefan Farestam
Mobile: +46 70 649 6838
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
eCryptfs-users mailing list
eCryptfs-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecryptfs-users
