On Tue, Oct 28, 2008 at 2:01 PM, J Fernyhough <[EMAIL PROTECTED]> wrote: > I don't get anything like that on my dmesg, though I do get an error: > > [ 128.608120] ecryptfs_parse_options: eCryptfs: unrecognized option 'rw' > [ 128.608132] ecryptfs_parse_options: eCryptfs: unrecognized option 'user=j'
These are benign noise. We're silencing those upstream, probably won't make it to Intrepid, though. :-Dustin -- ecryptfs-setup-private accepts but cannot add to keyring a mount passphrase containing some characters https://bugs.launchpad.net/bugs/290064 You received this bug notification because you are a member of eCryptfs, which is subscribed to ecryptfs-utils in ubuntu. Status in “ecryptfs-utils” source package in Ubuntu: Confirmed Bug description: Binary package hint: ecryptfs-utils ~$ lsb_release -rd Description: Ubuntu 8.10 Release: 8.10 $ apt-cache policy ecryptfs-utils ecryptfs-utils: Installed: 53-1ubuntu11 Trying to set up a ~/Private with a mount passphrase containing any parentheses ( "(",")" ) will initially be accepted but the script will fail on trying to add the passphrase to the keyring: # Add the passphrase to current keyring # On subsequent logins, this should be handled by "pam_ecryptfs.so unwrap" response=`printf "$MOUNTPASS" | ecryptfs-add-passphrase -` if [ $? -ne 0 ]; then error "Could not add passphrase to the current keyring" fi This has worked previously. _______________________________________________ Mailing list: https://launchpad.net/~ecryptfs Post to : [email protected] Unsubscribe : https://launchpad.net/~ecryptfs More help : https://help.launchpad.net/ListHelp
