ecryptfs team mailing list archive

[Tyler Hicks <tyhicks@xxxxxxxxxxxxxxxxxx>]

Certain options like "rw" should be stripped from the mount options
string before being passed to mount().  These stripped options are
represented in the mountflags argument (see the section 2 mount man
page).  The original eCryptfs mount helper (mount.ecryptfs) does this,
but the mount.ecryptfs_private helper does not.  I'll write a patch to
fix this.

As for the warning about "user=derjkan" option, I think that is a valid
warning.  Neither the kernel or the userspace side of things seem to use
that option.  "uid=<uid>" and "user" are valid options, I'm guessing
that we meant to use one (or both) of those options instead.  Dustin,
any comments on this?

-- 
ecryptfs unrecognized options are logged
https://bugs.launchpad.net/bugs/277723
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in eCryptfs - Enterprise Cryptographic Filesystem: Confirmed
Status in “ecryptfs-utils” source package in Ubuntu: Confirmed

Bug description:
Binary package hint: ecryptfs-utils


Upon reboot and login, these messages are logged:

ecryptfs_parse_options: eCryptfs: unrecognized option 'rw'
ecryptfs_parse_options: eCryptfs: unrecognized option 'user=derkjan'
padlock: VIA PadLock not detected.

For each login, these messages are logged:
ecryptfs_parse_options: eCryptfs: unrecognized option 'rw'
ecryptfs_parse_options: eCryptfs: unrecognized option 'user=derkjan'

Otherwise everything works as advertised.
software version is ecryptfs-utils 53-1ubuntu8