linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: support access control via key management
Date: Mon, 21 Mar 2016 08:39:38 -0700	[thread overview]
Message-ID: <20160321153938.GB27230@infradead.org> (raw)
In-Reply-To: <20160315163725.GA78436@jaegeuk.gateway>

On Tue, Mar 15, 2016 at 09:37:25AM -0700, Jaegeuk Kim wrote:
> I agree that I must follow FS convention here.
> But, in order to make this clear out, could you please elaborate why this is not
> allowed?
> 
> I wrote this patch totally based on per-file encryption in which users cannot
> access their files if they have no right key.
> The only difference is that this controls user access with a key only, neither
> encrypting file data nor dentries.
> 
> This was initiated by UX in android letting nobody be able to access the files
> that owner wants to protect by passcode or fingerprint.
> 
> Does it make no sense to support this by filesystems?

I don't think it does.  But if you want to argue for it you should

 a) support it in the VFS
 b) document the exact semantics
 c) ensure linux-man and linux-api are on the Cc list.

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140

      reply	other threads:[~2016-03-21 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10  0:52 [PATCH] f2fs: support access control via key management Jaegeuk Kim
2016-03-10  2:05 ` kbuild test robot
2016-03-10  2:18 ` kbuild test robot
2016-03-15  7:24 ` Christoph Hellwig
2016-03-15 16:37   ` Jaegeuk Kim
2016-03-21 15:39     ` Christoph Hellwig [this message]

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=20160321153938.GB27230@infradead.org \
    --to=hch@infradead.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).