All of lore.kernel.org
 help / color / mirror / Atom feed
From: Serge Hallyn <serue@us.ibm.com>
To: "Timothy R. Chavez" <tinytim@us.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH] (#3) file system auditing
Date: Thu, 28 Apr 2005 16:50:02 -0500	[thread overview]
Message-ID: <1114725002.25299.8.camel@serge> (raw)
In-Reply-To: <1114720285.6554.88.camel@localhost>

On Thu, 2005-04-28 at 15:31 -0500, Timothy R. Chavez wrote:
> On Wed, 2005-04-27 at 00:28 +0100, Christoph Hellwig wrote:
> > On Tue, Apr 26, 2005 at 04:04:46PM -0500, Timothy R. Chavez wrote:
> > > Hello,
> > > 
> > > The audit subsystem is currently incapable of auditing a file system
> > > object based on its location and name.
> > 
> 
> Hello Christoph,
> 
> I apologize for the delay in my response.  Thank you for your response.
> I'll try to be succinct.
> 
> > Which doesn't make sense in our world of per-process namespaces.  

AFAICT, it does so long as we are trying to audit non-admin users.  I
may be in a different namespace from the admin, but so long only the
admin can mount over /etc, the auditing should still happen.  An admin
can mess us up by mounting /root/dummy/etc on top of /etc, but we expect
the admin to know what he is doing.

Note that this patch is not auditing based on full pathname.  It audits
based on the parent directory and filename.  So even if /etc is bind
mounted onto /mnt/root/etc, accessing /mnt/root/etc/passwd will still
trigger an audit entry.

Am I missing something?  How do namespaces mess this up?

thanks,
-serge

-- 
Serge Hallyn <serue@us.ibm.com>


      reply	other threads:[~2005-04-28 21:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-26 21:04 [RFC][PATCH] (#3) file system auditing Timothy R. Chavez
2005-04-26 23:28 ` Christoph Hellwig
2005-04-27 11:57   ` Stephen Smalley
2005-04-28 20:31   ` Timothy R. Chavez
2005-04-28 21:50     ` Serge Hallyn [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=1114725002.25299.8.camel@serge \
    --to=serue@us.ibm.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tinytim@us.ibm.com \
    /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.