From: Karel Zak <kzak@redhat.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>,
Eric Biggers <ebiggers@google.com>,
David Gstir <david@sigma-star.at>,
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: Mon, 24 Oct 2016 14:49:37 +0200 [thread overview]
Message-ID: <20161024124937.bxohuapjqns3m2dy@ws.net.home> (raw)
In-Reply-To: <0bef3877-060e-b722-0354-3a5508219e23@nod.at>
On Wed, Oct 19, 2016 at 01:35:54PM +0200, Richard Weinberger wrote:
> Hi!
>
> Since file level encryption has more than one user, currently ext4, f2fs and soon ubifs
> it would be nice to have a single tool to control fscrypto from userspace.
>
> For ext4 we have already at least two tools, one as part of e2fsprogs and another
> one on github[0]. IMHO the latter one is much more user friendly and intuitive to use.
> I as unable to find the userspace tool for f2fs.
>
> That said, what about implementing such a tool as part of util-linux to control
> fscrypto? We (David and I) would volunteer.
I have nothing against this plan (add to util-linux) if ext4, f2fs and
ubifs guys agree too.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2016-10-24 12:49 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
2016-11-30 21:00 ` Theodore Ts'o
2016-10-24 12:49 ` Karel Zak [this message]
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=20161024124937.bxohuapjqns3m2dy@ws.net.home \
--to=kzak@redhat.com \
--cc=david@sigma-star.at \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--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=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).