Ok, so I can explain how to reproduce this. First, the good news is that
the kernel is now showing less scary output:
[ 3466.471436] Could not find key with description: [c699b2046e6675aa]
[ 3466.471443] process_request_key_err: No key
[ 3466.471448] ecryptfs_parse_packet_set: Could not find a usable
authentication token
[ 3466.471454] Valid eCryptfs headers not found in file header region or xattr
region, inode 1311644
[ 3466.471460] Either the lower file is not in a valid eCryptfs format, or the
key could not be retrieved. Plaintext passthrough mode is not enabled;
returning -EIO
so I think this is fix released.
I am using mount.ecryptfs_private. I have a bunch of .conf and .sig files
under ~/.ecryptfs. One in particular has the x.sig file with a signature
for a passphrase different than the one actually in use for that fs. So
if I have that passphrase loaded in my keyring, then
mount.ecryptfs x
works, but of course I can't then read the files in that fs. The error being
shown now is appropriate and helpful. So I'd call this fix released.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/767145
Title:
BUG: unable to handle kernel paging request at ffffff82; EIP is at
key_put+0xc/0x30
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/767145/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
