Ubuntu
ecryptfs-utils package

ecryptfs unrecognized options are logged

Bug #277723 reported by Derkjan de Haan
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
eCryptfs
Fix Released
Low
Dustin Kirkland 
ecryptfs-utils (Ubuntu)
Fix Released
Low
Dustin Kirkland 

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

Tags: pet-bug
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Thanks for the bug report.

I can confirm the messages, and agree they are annoying. I'm going to forward the bug upstream and fix it there.

Thanks!
:-Dustin

Changed in ecryptfs-utils:
importance: Undecided → Low
status: New → Confirmed
Changed in ecryptfs:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

This actually looks like an ecryptfs kernel message, rather than something reported in ecryptfs-utils userspace.

I'm forwarding this to Tyler. Any ideas?

:-Dustin

Revision history for this message
Tyler Hicks (tyhicks) wrote :

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?

Dustin Kirkland  (kirkland)
Changed in ecryptfs-utils:
assignee: nobody → kirkland
Changed in ecryptfs:
assignee: nobody → kirkland
Revision history for this message
Tyler Hicks (tyhicks) wrote :

Here's an untested patch to fix the complaint about the "rw" option. I am just reusing the code from the original mount helper, so I don't foresee any problems. The patch applies to the current ecryptfs-utils git tree.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Committed to upstream git.

http://git.kernel.org/?p=linux/kernel/git/mhalcrow/ecryptfs-utils.git;a=commit;h=818b5930c8cfc7935099a7a2b2ad21255602b9dd

Will be in the -69 release.

:-Dustin

Changed in ecryptfs:
status: Confirmed → Fix Committed
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Patch attached for Jaunty. Requesting sponsorship.

:-Dustin

Changed in ecryptfs-utils:
status: Confirmed → In Progress
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Updated, cleaner patch attached. Committed against upstream:
 * http://git.kernel.org/?p=linux/kernel/git/mhalcrow/ecryptfs-utils.git;a=commit;h=34cf8dffd3a33c97fcacc49242633bd145079198

Requesting sponsorship.

:-Dustin

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ecryptfs-utils - 68-1ubuntu2

---------------
ecryptfs-utils (68-1ubuntu2) jaunty; urgency=low

  * debian/patches/05-mount_opts.dpatch: Clean up mount options, LP: #277723

 -- Dustin Kirkland <email address hidden> Mon, 05 Jan 2009 15:34:05 -0600

Changed in ecryptfs-utils:
status: In Progress → Fix Released
Dustin Kirkland  (kirkland)
Changed in ecryptfs:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.