From: "Timothy R. Chavez" <tinytim@us.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Steve Grubb <sgrubb@redhat.com>, Greg KH <greg@kroah.com>,
Andrew Morton <akpm@osdl.org>,
linux-audit@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
Mounir Bsaibes <mbsaibes@us.ibm.com>,
Serge Hallyn <serue@us.ibm.com>,
Alexander Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Klaus Weidner <klaus@atsec.com>, Chris Wright <chrisw@osdl.org>,
Stephen Smalley <sds@tycho.nsa.gov>, Robert Love <rml@novell.com>,
Christoph Hellwig <hch@infradead.org>,
Daniel H Jones <danjones@us.ibm.com>,
Amy Griffis <amy.griffis@hp.com>,
Maneesh Soni <maneesh@in.ibm.com>
Subject: Re: [PATCH] audit: file system auditing based on location and name
Date: Thu, 7 Jul 2005 17:08:31 -0500 [thread overview]
Message-ID: <200507071708.32451.tinytim@us.ibm.com> (raw)
In-Reply-To: <1120771909.3198.32.camel@laptopd505.fenrus.org>
On Thursday 07 July 2005 16:31, Arjan van de Ven wrote:
> On Thu, 2005-07-07 at 15:48 -0400, Steve Grubb wrote:
>
> > Tim's code lets you say I want change notification to this file only. The
> > notification follows the audit format with all relavant pieces of information
> > gathered at the time of the event and serialized with all other events.
>
> well can't you sort of do that based on (selinux) security context of
> the file already? after all that's part of the inode already. Isn't that
> finegrained enough?
>
Provided you make it that far, yes, SE Linux _could_ be used to provide
similar functionality. But, what if you bottom out on a DAC decision?
[foo@liltux /]$ cat /etc/shadow
cat: /etc/shadow: Permission denied
-tim
next prev parent reply other threads:[~2005-07-07 22:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 16:54 [PATCH] audit: file system auditing based on location and name Timothy R. Chavez
2005-07-06 17:17 ` Greg KH
2005-07-06 20:23 ` Timothy R. Chavez
2005-07-06 23:50 ` Greg KH
2005-07-07 1:33 ` Steve Grubb
2005-07-07 18:15 ` Greg KH
2005-07-07 18:49 ` Steve Grubb
2005-07-07 19:04 ` Greg KH
2005-07-07 19:48 ` Steve Grubb
2005-07-07 21:31 ` Arjan van de Ven
2005-07-07 22:08 ` Timothy R. Chavez [this message]
2005-07-07 22:51 ` serue
2005-07-08 5:33 ` Arjan van de Ven
2005-07-08 5:48 ` James Morris
2005-07-08 17:48 ` Greg KH
2005-07-07 16:26 ` Timothy R. Chavez
2005-07-07 18:10 ` Greg KH
2005-07-07 18:16 ` David Woodhouse
2005-07-07 18:18 ` Greg KH
2005-07-07 19:49 ` Timothy R. Chavez
2005-07-08 17:46 ` Greg KH
2005-07-08 19:48 ` Timothy R. Chavez
2005-07-10 18:59 ` Greg KH
[not found] ` <OF993CB74B.E135A576-ON8725703B.00568CD6-0525703B.005814C3@us.ibm.com>
2005-07-11 17:13 ` Greg KH
2005-07-09 1:10 ` Chris Wright
2005-07-09 2:10 ` Timothy R. Chavez
2005-07-07 6:40 ` Arjan van de Ven
2005-07-07 6:50 ` David Woodhouse
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=200507071708.32451.tinytim@us.ibm.com \
--to=tinytim@us.ibm.com \
--cc=akpm@osdl.org \
--cc=amy.griffis@hp.com \
--cc=arjan@infradead.org \
--cc=chrisw@osdl.org \
--cc=danjones@us.ibm.com \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=klaus@atsec.com \
--cc=linux-audit@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=mbsaibes@us.ibm.com \
--cc=rml@novell.com \
--cc=sds@tycho.nsa.gov \
--cc=serue@us.ibm.com \
--cc=sgrubb@redhat.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.