From: James Morris <jmorris@namei.org>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Aaron Goidel <acgoide@tycho.nsa.gov>,
paul@paul-moore.com, selinux@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, dhowells@redhat.com, jack@suse.cz,
amir73il@gmail.com, sds@tycho.nsa.gov,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] fanotify, inotify, dnotify, security: add security hook for fs notifications
Date: Fri, 12 Jul 2019 13:29:32 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1907121327150.22212@namei.org> (raw)
In-Reply-To: <4fd98c88-61a6-a155-5028-db22a778d3c1@schaufler-ca.com>
On Wed, 10 Jul 2019, Casey Schaufler wrote:
> On 7/10/2019 6:34 AM, Aaron Goidel wrote:
>
> > Furthermore, fanotify watches grant more power to
> > an application in the form of permission events. While notification events
> > are solely, unidirectional (i.e. they only pass information to the
> > receiving application), permission events are blocking. Permission events
> > make a request to the receiving application which will then reply with a
> > decision as to whether or not that action may be completed.
>
> You're not saying why this is an issue.
Also in the description, please explain the issues with read and write
notifications and why a simple 'read' permission is not adequate.
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2019-07-12 3:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 13:34 [RFC PATCH] fanotify, inotify, dnotify, security: add security hook for fs notifications Aaron Goidel
2019-07-10 14:55 ` Amir Goldstein
2019-07-10 17:25 ` [Non-DoD Source] " Aaron Goidel
2019-07-10 16:38 ` Casey Schaufler
2019-07-10 16:49 ` Randy Dunlap
2019-07-10 16:55 ` Casey Schaufler
2019-07-10 17:18 ` Joe Perches
2019-07-10 17:22 ` Joe Perches
2019-07-10 17:53 ` Randy Dunlap
2019-07-10 18:39 ` Stephen Smalley
2019-07-10 20:09 ` Casey Schaufler
2019-07-12 3:29 ` James Morris [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=alpine.LRH.2.21.1907121327150.22212@namei.org \
--to=jmorris@namei.org \
--cc=acgoide@tycho.nsa.gov \
--cc=amir73il@gmail.com \
--cc=casey@schaufler-ca.com \
--cc=dhowells@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@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).