ecryptfs team mailing list archive

[J Fernyhough <j.fernyhough@xxxxxxxxx>]

(Had to use "keyctl" not "keyutils")

OK, this bug is invalid. It's not the parentheses that do it.

I've tested with other passphrases and they all work - it just seems to
fail with the one I want to use. If I change one character it works,
change the order of characters it works, another passphrase of the same
length and complexity works, keyctl clear @u doesn't affect the outcome,
I've also tried rm -fR .ecryptfs and starting again.

I assumed this was with the keyring, but the passphrase has been
accepted before. I reinstalled Intrepid (surprise) and wanted to recover
my user's Private. I can successfully sudo mount -t ecryptfs ~/.Private
priv, enter the correct details and it works, so I have been using the
obvious workaround of using a different passphrase. I would love to give
you the passphrase to investigate but it's in use for other things
too... :/

** Changed in: ecryptfs-utils (Ubuntu)
       Status: Incomplete => Invalid

-- 
ecryptfs-setup-private accepts but cannot add to keyring a mount passphrase containing parentheses
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: Invalid

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.