From: Richard Weinberger <richard@nod.at>
To: Joe Richey <joerichey@google.com>
Cc: 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>,
Eric Biggers <ebiggers@google.com>,
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: Tue, 29 Nov 2016 22:59:28 +0100 [thread overview]
Message-ID: <87d9b3aa-684d-856a-0dcd-f960923f2484@nod.at> (raw)
In-Reply-To: <CAKpBdu1+k94WmwxeZ2Hyu5=ifNprPA0YedRm2xps-ooyVHTwhg@mail.gmail.com>
Joe,
On 29.11.2016 22:42, Joe Richey wrote:
> Hi Richard,
>
> I'm Joe Richey, and I work on Mike's team. We've been playing around
> with a few design
> ideas regarding a tool for managing filesystem encryption. After going
> though some iterations
> with Ted, we have a fairly good idea about where to head design wise,
> and I'm working on a
> design document for it. It's a bit preliminary at this point, but I
> can share it if you want.
>
> Our goal is to have a finished doc by end of Q4 and then get your and
> Jaegeuk's feedback.
Thanks for your quick response!
I hoped you had already some code, but having a decent design document
is also nice. I'm eager to read it.
Do you also plan to address d/page cache related issues?
i.e. when two users are logged into the system user rw
is able to see decrypted file names and contents in /home/dags/
if user dags installs a key and accessed a file.
Or files in /home/dags/ are still readable even after
user dags purged the key.
The tool could play games with CLONE_NEWNS to hide directories.
To provide a correct "logout" we could expose shrink_dcache_parent()
to usespace such that the emerging tool can purge the key and flush
the dcache on the encrypted directory. But I fear exposing shrink_dcache_parent()
is not a good idea. :-)
Just some random ideas...
Thanks,
//richard
next prev parent reply other threads:[~2016-11-29 22:00 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 [this message]
2016-11-30 0:04 ` Eric Biggers
2016-11-30 8:27 ` Richard Weinberger
2016-12-03 0:40 ` Eric Biggers
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=87d9b3aa-684d-856a-0dcd-f960923f2484@nod.at \
--to=richard@nod.at \
--cc=david@sigma-star.at \
--cc=ebiggers@google.com \
--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=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).