The version mismatch does not come from the kernel 2.6.32, I've just reproduce it with the official 2.6.31-15-generic.
** Description changed: Binary package hint: ecryptfs-utils Another stupid use case: if you insert a key in the keyring using the signature from ~/.ecryptfs/Private.sig as description, and something wrong as the passprase, you don't get a meaningful message saying that the passphrase is not the right one. Instead, you get an error from mount. I know I shouldn't be doing that, but getting clear error messages always helps debugging. $ keyctl clear @u $ keyctl add user [signature] stuff @u 896838280 - $ mount.ecryptfs_private + $ mount.ecryptfs_private mount: Invalid argument - dmesg shows weird errors, maybe meaning something else is going wrong? [ 3676.632918] ecryptfs_verify_version: Major version number mismatch. Expected [0]; got [101] [ 3676.632926] Data structure version mismatch. Userspace tools must match eCryptfs kernel module with major version [0] and minor version [4] [ 3676.632930] Could not find valid key in user session keyring for sig specified in mount option: [signature] [ 3676.632934] One or more global auth toks could not properly register; rc = [-22] [ 3676.632937] Error parsing options; rc = [-22] ProblemType: Bug Architecture: i386 Date: Wed Dec 9 11:22:27 2009 DistroRelease: Ubuntu 9.10 Package: ecryptfs-utils 81-0ubuntu3 ProcEnviron: - LANGUAGE=fr_FR.UTF-8 - PATH=(custom, user) - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + LANGUAGE=fr_FR.UTF-8 + PATH=(custom, user) + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: ecryptfs-utils - Uname: Linux 2.6.32-020632rc8-generic i686 + Uname: Linux 2.6.31-15-generic i686 -- mount.ecryptfs_private fails with: "mount: Invalid argument" when wrong passphrase inserted into the keyring https://bugs.launchpad.net/bugs/494412 You received this bug notification because you are a member of eCryptfs, which is subscribed to ecryptfs-utils in ubuntu. Status in “ecryptfs-utils” package in Ubuntu: New Bug description: Binary package hint: ecryptfs-utils Another stupid use case: if you insert a key in the keyring using the signature from ~/.ecryptfs/Private.sig as description, and something wrong as the passprase, you don't get a meaningful message saying that the passphrase is not the right one. Instead, you get an error from mount. I know I shouldn't be doing that, but getting clear error messages always helps debugging. $ keyctl clear @u $ keyctl add user [signature] stuff @u 896838280 $ mount.ecryptfs_private mount: Invalid argument dmesg shows weird errors, maybe meaning something else is going wrong? [ 3676.632918] ecryptfs_verify_version: Major version number mismatch. Expected [0]; got [101] [ 3676.632926] Data structure version mismatch. Userspace tools must match eCryptfs kernel module with major version [0] and minor version [4] [ 3676.632930] Could not find valid key in user session keyring for sig specified in mount option: [signature] [ 3676.632934] One or more global auth toks could not properly register; rc = [-22] [ 3676.632937] Error parsing options; rc = [-22] ProblemType: Bug Architecture: i386 Date: Wed Dec 9 11:22:27 2009 DistroRelease: Ubuntu 9.10 Package: ecryptfs-utils 81-0ubuntu3 ProcEnviron: LANGUAGE=fr_FR.UTF-8 PATH=(custom, user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ecryptfs-utils Uname: Linux 2.6.31-15-generic i686 _______________________________________________ Mailing list: https://launchpad.net/~ecryptfs Post to : [email protected] Unsubscribe : https://launchpad.net/~ecryptfs More help : https://help.launchpad.net/ListHelp
