Red Hat Bugzilla – Bug 553629
when using passwd_file together with salt option mount of ecryptfs fails
Last modified: 2013-04-12 16:34:28 EDT
Description of problem: # cat ecryptfs-passwd passphrase_passwd=xxx # /sbin/mount.ecryptfs .crypt/ .crypt/ -o "key=passphrase:passphrase_passwd_file=/root/ecryptfs-passwd:passphrase_salt=1234567890abcdef,ecryptfs_key_bytes=16,ecryptfs_cipher=aes,no_sig_cache,verbosity=0,verbose" Error attempting to evaluate mount options: [-14] Bad address Check your system logs for details on why this happened. Try updating your ecryptfs-utils package, and/or submit a bug report on https://launchpad.net/ecryptfs See unsuccessful-log attachment that contains mount.ecryptfs messages in /var/log/messages Version-Release number of selected component (if applicable): RHEL5.5-Server-20091227.0 x86_64 kernel-2.6.18-183.el5 ecryptfs-utils-75-5.el5 How reproducible: 100% Steps to Reproduce: 1. mount filesystem with passphrase_passwd_file and passhprase_salt options together 2. 3. Actual results: mount fails Expected results: mount succeeds Additional info: Ommiting passphrase_salt from options allows filesystem to be mounted. # /sbin/mount.ecryptfs .crypt/ .crypt/ -o "key=passphrase:passphrase_passwd_file=/root/ecryptfs-passwd,ecryptfs_key_bytes=16,ecryptfs_cipher=aes,no_sig_cache,verbosity=0,verbose" Attempting to mount with the following options: ecryptfs_unlink_sigs ecryptfs_key_bytes=16 ecryptfs_cipher=aes ecryptfs_sig=1b77138d91206e66 Mounted eCryptfs # mount | grep ecryptfs /root/.crypt on /root/.crypt type ecryptfs (rw,ecryptfs_sig=1b77138d91206e66,ecryptfs_unlink_sigs,ecryptfs_key_bytes=16,ecryptfs_cipher=aes) See successful-log attachment that contains mount.ecryptfs messages in /var/log/messages.
Created attachment 382466 [details] unsuccessful-log
Created attachment 382467 [details] successful-log
Created attachment 407063 [details] patch to fix this
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1503.html