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: Detecting execution of files in rwtab
Date: Mon, 16 Oct 2017 21:51:04 -0400	[thread overview]
Message-ID: <2550586.E2Bae6L3A0@x2> (raw)
In-Reply-To: <CAELdiYGQp3tioHKh4E=Zjp7jntdB6e=v92v=mrKUhyPCcSf+Pw@mail.gmail.com>

On Monday, October 16, 2017 1:21:50 PM EDT Kevin Sullivan wrote:
> Sorry if this topic has already been discussed, but I was unable to find
> information about it in the mailing list.
> 
> I am running auditd on a machine that is configured with readonly-root
> support. For this configuration to work, I have files listed in
> /etc/rwtab.d/ that need to be read-write, but are on my hard-drive that is
> read-only.
> 
> So if I add an audit rule for a random file:
> 
> # auditctl -w /etc/rc.d/rc.local -p x -k rclocal
> 
> If /etc/rc.d/rc.local is mounted in a tmpfs (because of readonly-root),
> running rc.local will not produce an event. If I unmount /etc/rc.d/rc.local
> and run it, an event will be generated.
> 
> How am I supposed to audit files that are mounted in tmpfs due to rwtab and
> readonly-root?

I would like to help you, but I'm having a hard time figuring out what you are 
talking about. Can you give the steps to reproduce the problem on a file in 
some directory like /opt/bug-reproducer? List the shell commands needed to 
setup the test environment, how to test it, and how you search to see that 
nothing is there. That would make it easier for us to see the problem on our 
own system and determine if there is a bug or logical explanation.

-Steve

      reply	other threads:[~2017-10-17  1:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 17:21 Detecting execution of files in rwtab Kevin Sullivan
2017-10-17  1:51 ` Steve Grubb [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=2550586.E2Bae6L3A0@x2 \
    --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