From: lkml@serverphorums.com
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/7] eCryptfs: added support for the encrypted key type
Date: Fri, 14 Dec 2012 13:00:33 +0100 (CET) [thread overview]
Message-ID: <1c1575f5e47b34a02741b86d367a8617.LinuxKernel@www.serverphorums.com> (raw)
Hi there,
Either this is completely braindead, or I'm missing something very obvious.
Why mess up encrypted keys with various "format" fixes.
I hope this doesn't start a trend.
The right (and disturbingly simpler) approach to fixing the auth_token vs.
raw key material issue would be to put the fix in eCryptfs.
In fact, all the relevant bits for filling the token from the key_desc/sig should be moved
from security/keys/encrypted/ecryptfs_format.c to fs/ecryptfs/ecryptfs_kernel.h,
and all the format cruft in encrypted-keys reverted.
Then pretty much any "default" encrypted key could be used for ecryptfs…
What am I missing?
--@;
---
posted at http://www.serverphorums.com
http://www.serverphorums.com/read.php?12,341340,618745#msg-618745
next reply other threads:[~2012-12-14 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 12:00 lkml [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-27 11:45 Roberto Sassu
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=1c1575f5e47b34a02741b86d367a8617.LinuxKernel@www.serverphorums.com \
--to=lkml@serverphorums.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®