From: Eric Biggers <ebiggers@google.com>
To: Richard Weinberger <richard@nod.at>
Cc: Joe Richey <joerichey@google.com>,
Michael Halcrow <mhalcrow@google.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
kzak@redhat.com, "Theodore Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
David Gstir <david@sigma-star.at>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFD] Common userspace tool for fscypto
Date: Fri, 2 Dec 2016 16:40:40 -0800 [thread overview]
Message-ID: <20161203004040.GB3508@google.com> (raw)
In-Reply-To: <3d354949-0051-3f3a-f8ac-8dd99e9adc0f@nod.at>
On Wed, Nov 30, 2016 at 09:27:28AM +0100, Richard Weinberger wrote:
>
> BTW: This limitations needs to be clearly documented somewhere.
> Usually an user thinks that only she can access encrypted files...
>
> Thanks,
> //richard
For what it's worth, I've been making a few updates to the public design
document for ext4 encryption based on what's actually upstream now:
https://docs.google.com/document/d/1ft26lUQyuSpiu6VleP70_npaWdRfXFoNnB8JYnykNTg
It still needs work, though. It doesn't really answer the questions about
access control and key revocation, for example, and of course now the upstream
code isn't actually ext4 specific anymore.
At some point it might be nice to write some in-tree documentation for fscrypto,
e.g. a file Documentation/filesystems/fscrypto.txt.
Eric
next prev parent reply other threads:[~2016-12-03 0:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 11:35 [RFD] Common userspace tool for fscypto Richard Weinberger
2016-10-19 17:36 ` Michael Halcrow
2016-10-24 11:59 ` Richard Weinberger
2016-11-29 20:48 ` Richard Weinberger
2016-11-29 21:42 ` Joe Richey
2016-11-29 21:59 ` Richard Weinberger
2016-11-30 0:04 ` Eric Biggers
2016-11-30 8:27 ` Richard Weinberger
2016-12-03 0:40 ` Eric Biggers [this message]
2016-11-30 21:00 ` Theodore Ts'o
2016-10-24 12:49 ` Karel Zak
2016-10-24 13:28 ` Theodore Ts'o
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=20161203004040.GB3508@google.com \
--to=ebiggers@google.com \
--cc=david@sigma-star.at \
--cc=jaegeuk@kernel.org \
--cc=joerichey@google.com \
--cc=kzak@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@google.com \
--cc=richard@nod.at \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).