[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1341968751-28331-1-git-send-email-tsally@atomicpeace.com>
Date: Tue, 10 Jul 2012 21:05:50 -0400
From: Tim Sally <tsally@...micpeace.com>
To: tyhicks@...onical.com, dustin.kirkland@...zang.com
Cc: ecryptfs@...r.kernel.org, linux-kernel@...r.kernel.org,
Tim Sally <tsally@...micpeace.com>
Subject: [PATCH 0/1] Check for eCryptfs cipher support at mount time.
eCryptfs will mount with any cipher supported by the crypto subsystem,
even if the cipher is not supported by eCryptfs itself. An error will
not occur until a write. This change checks for eCryptfs cipher
support at mount time and will not mount the filesystem if the cipher
is not supported.
The cipher name and blocksize are retrieved from ecryptfs_key_tfm
because it will assign a default block size upon creation if none
is specified in the mount options.
This issue originally reported by Tyler Hicks in 03/2009.
https://bugs.launchpad.net/ecryptfs/+bug/338914
Thanks,
Tim
Tim Sally (1):
eCryptfs: check for eCryptfs cipher support at mount
fs/ecryptfs/main.c | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
--
1.7.10.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists