public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: lists_todd@mac.com
Cc: linux-audit@redhat.com
Subject: Re: peculiar disappearance of most audit rules
Date: Mon, 21 Apr 2014 15:03:28 -0400	[thread overview]
Message-ID: <1398107008.2596.2.camel@flatline.rdu.redhat.com> (raw)
In-Reply-To: <720F8F1C-2248-4BD7-9164-818F816662A1@mac.com>

On Mon, 2014-04-21 at 11:35 -0700, lists_todd@mac.com wrote:
> 
> On Apr 21, 2014, at 11:28 AM, Steve Grubb <sgrubb@redhat.com> wrote:
> 
> > What happens is that the text path that you put in a watch is a
> > human 
> > convenience. The kernel doesn't understand strings, it understands
> > numbers. It 
> > changes the path into device and inode information.
> 
> 
> Cool. So I am guessing the rule works even if someone creates a hard
> link to the same watched path and access files through that other
> path?

As I remember, and it's been a long time, watches should survive even if
the object being watched is deleted and recreated.  I seemed to remember
it was only if the parent directory is deleted that rules get evicted.

So that doesn't explain it for /boot!  Pretty darn hard to delete /!
But it could easily make sense for your other areas being watched...

But yes, if you watch /etc/shadow and someone accesses that inode
through another hard link, you will get audit records...

  reply	other threads:[~2014-04-21 19:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21 17:49 peculiar disappearance of most audit rules Peter Grandi
2014-04-21 18:28 ` Steve Grubb
2014-04-21 18:35   ` lists_todd
2014-04-21 19:03     ` Eric Paris [this message]
2014-04-21 20:49   ` Peter Grandi
2014-04-22 20:53     ` Peter Grandi
2014-04-22 21:46       ` Steve Grubb
2014-04-23  8:04       ` Peter Grandi
2014-04-23 14:34         ` Eric Paris
2014-04-27 20:33           ` Peter Grandi
2014-11-05 16:55             ` Richard Guy Briggs

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=1398107008.2596.2.camel@flatline.rdu.redhat.com \
    --to=eparis@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=lists_todd@mac.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