All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: [RFC] Virtual Key Fields
Date: Mon, 24 Mar 2008 09:52:28 -0400	[thread overview]
Message-ID: <200803240952.28242.sgrubb@redhat.com> (raw)
In-Reply-To: <1206366134.3192.14.camel@localhost.localdomain>

On Monday 24 March 2008 09:42:14 Eric Paris wrote:
> > Auditctl will also allow delete all rules matching a key. This will allow
> > the admin or a program to delete a set of rules related to just a
> > particular key and leave all other rules intact.
>
> How does this work?  This is a completely new concept and it seems like
> it should be a second patch after you have multiple keys in to start
> with.

This is all in user space so no kernel changes are needed.


> auditctl -a exit,always -w /tmp/file1 -k file1 -k shared-key
> auditctl -a exit,always -w /tmp/file2 -k file2 -k shared-key
>
> now if I say (and i'm just guessing your new syntax):
>
> auditctl -d -k shared-key

I was only going to change the '-D' option (delete all). Assuming this was 
typed:

auditctl -D -k shared-key

You have no rules left which is the same as if you did not have the -k added. 
If however, you have this loaded:

-a exit,always -w /tmp/file1 -k file1 -k my-file-key -k ids-file-high
-a exit,always -w /tmp/file2 -k file2 -k another-key -k ids-file-high

auditctl -D -k another-key

will just delete the second rule.

auditctl -D -k ids-file-high

will delete them all.

-Steve

  reply	other threads:[~2008-03-24 13:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 13:27 [RFC] Virtual Key Fields Steve Grubb
2008-03-24 13:42 ` Eric Paris
2008-03-24 13:52   ` Steve Grubb [this message]
2008-03-24 14:01     ` Eric Paris
2008-03-24 14:38 ` LC Bruzenak
2008-03-24 15:44 ` Klaus Heinrich Kiwi

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=200803240952.28242.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=eparis@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 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.