diff options
author | Tyler Hicks <tyhicks@linux.vnet.ibm.com> | 2009-03-13 13:51:59 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-03-14 11:57:22 -0700 |
commit | 84814d642a4f1f294bd675ab11aae1ca54c6cedb (patch) | |
tree | 4ae91cce54c8d9578dc3217b6454a921b91833a3 /mm | |
parent | 15e7b8767605dc0cb9bd4594caabfec392385210 (diff) | |
download | kernel-crypto-84814d642a4f1f294bd675ab11aae1ca54c6cedb.tar.gz kernel-crypto-84814d642a4f1f294bd675ab11aae1ca54c6cedb.tar.xz kernel-crypto-84814d642a4f1f294bd675ab11aae1ca54c6cedb.zip |
eCryptfs: don't encrypt file key with filename key
eCryptfs has file encryption keys (FEK), file encryption key encryption
keys (FEKEK), and filename encryption keys (FNEK). The per-file FEK is
encrypted with one or more FEKEKs and stored in the header of the
encrypted file. I noticed that the FEK is also being encrypted by the
FNEK. This is a problem if a user wants to use a different FNEK than
their FEKEK, as their file contents will still be accessible with the
FNEK.
This is a minimalistic patch which prevents the FNEKs signatures from
being copied to the inode signatures list. Ultimately, it keeps the FEK
from being encrypted with a FNEK.
Signed-off-by: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
Cc: Serge Hallyn <serue@us.ibm.com>
Acked-by: Dustin Kirkland <kirkland@canonical.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions