public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: linux-audit: reconstruct path names from syscall events?
Date: Fri, 7 Oct 2011 14:02:41 -0400	[thread overview]
Message-ID: <201110071402.41508.sgrubb@redhat.com> (raw)
In-Reply-To: <4E8F34D7.1030407@schaufler-ca.com>

On Friday, October 07, 2011 01:20:23 PM Casey Schaufler wrote:
> I would be delighted if someone came up with the fiendishly
> clever solution to the issue. I am not going to bet on one
> in my lifetime.

It doesn't even need to be fiendishly clever to be useful. Using the /etc/shadow 
analogy, What we get now is just shadow. Shadow where? /etc? /var/chroot/bind/etc? 
/backup/etc? Any clue would be helpful. Bind mounts, chroot, and namespaces all make 
it interesting, but just adding the dir as an aux record would make things so much 
better. We can solve the other problem another day.

-Steve

  reply	other threads:[~2011-10-07 18:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-17  0:12 linux-audit: reconstruct path names from syscall events? John Feuerstein
2011-10-01 12:31 ` Steve Grubb
2011-10-03 19:42   ` Casey Schaufler
2011-10-04 17:02     ` Steve Grubb
2011-10-04 22:09     ` John Feuerstein
2011-10-07 13:50       ` Eric Paris
2011-10-07 14:04         ` Steve Grubb
2011-10-07 17:20         ` Casey Schaufler
2011-10-07 18:02           ` Steve Grubb [this message]
2011-10-07 18:27           ` Eric Paris
2011-10-07 21:38             ` Casey Schaufler
2011-10-10 12:54               ` Steve Grubb
2012-10-09 23:09 ` Mark Moseley
2012-10-09 23:29   ` Al Viro
2012-10-09 23:39   ` Al Viro
2012-10-09 23:47     ` Mark Moseley
2012-10-09 23:54       ` Al Viro
2012-10-10 22:45         ` Mark Moseley
2012-10-10 23:00           ` Steve Grubb
2012-10-10 23:07             ` Mark Moseley
2012-10-11 17:27               ` Mark Moseley
2012-10-30  1:12                 ` Mark Moseley

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=201110071402.41508.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox