public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Sally <tsally@atomicpeace.com>
To: tyhicks@canonical.com, dustin.kirkland@gazzang.com
Cc: ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tim Sally <tsally@atomicpeace.com>
Subject: [PATCH 0/1] Check for eCryptfs cipher support at mount time.
Date: Tue, 10 Jul 2012 21:05:50 -0400	[thread overview]
Message-ID: <1341968751-28331-1-git-send-email-tsally@atomicpeace.com> (raw)

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


             reply	other threads:[~2012-07-11  1:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11  1:05 Tim Sally [this message]
2012-07-11  1:05 ` [PATCH 1/1] eCryptfs: check for eCryptfs cipher support at mount Tim Sally
2012-07-11 17:11   ` Tyler Hicks
2012-07-12 23:10     ` Tim Sally
2012-07-14  0:24       ` Tyler Hicks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1341968751-28331-1-git-send-email-tsally@atomicpeace.com \
    --to=tsally@atomicpeace.com \
    --cc=dustin.kirkland@gazzang.com \
    --cc=ecryptfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tyhicks@canonical.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox