ecryptfs file permissions broken with kernel 2.6.36-rc2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Undecided
|
Unassigned | ||
eCryptfs |
Fix Released
|
Critical
|
Tyler Hicks | ||
linux (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
There seems to be an incompatibility between kernel 2.6.36-rc2 and earlier kernel versions when using ecryptfs (I'm using ecryptfs-utils v83-0ubuntu3 on an ext4 file system).
The following output from "ls -il" shows the problem:
ls: cannot access enctest/file1: No such file or directory
ls: cannot access enctest/sub: No such file or directory
total 12
545077 -????????? ? ? ? ? ? file1
545075 -rw-r--r-- 1 root root 3 2010-08-24 08:53 file3-2.6.36
545078 d????????? ? ? ? ? ? sub
file2-2.6.36 was created after mounting the ecryptfs folder with kernel 2.6.36-rc2. The others were created after mounting with kernel 2.6.35.3. Their inodes and filenames look fine but the other information is corrupted.
Changed in ecryptfs: | |
assignee: | nobody → Tyler Hicks (tyhicks) |
importance: | Undecided → Critical |
status: | New → In Progress |
tags: | added: kernel-key |
It also seems that the filename created with 2.6.36-rc2 wasn't actually encrypted, although the folder _was_ mounted with ecryptfs and the option ecryptfs_ enable_ filename_ crypto= y when the file was created. The unmounted file system shows as:
drwxr-xr-x 2 root root 4096 2010-08-24 08:46 ECRYPTFS_ FNEK_ENCRYPTED. FWbHtjpMW4PshkQ YqeqfXg. U0JuQXr1L9kl5EZ f1rz1pCTkRUosaI lIjfE-- FNEK_ENCRYPTED. FWbHtjpMW4PshkQ YqeqfXg. U0JuQXr1L9kl5XI V47v4Cjghfg43P4 4xFJ---
-rw-r--r-- 1 root root 12288 2010-08-24 08:46 ECRYPTFS_
-rw-r--r-- 1 root root 12288 2010-08-24 08:53 file3-2.6.36
The contents of the file were encrypted, though.