public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Richard Guy Briggs <rgb@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Clear kernel audit buffer?
Date: Tue, 14 Jan 2014 09:47:15 -0500	[thread overview]
Message-ID: <20140114144715.GQ13431@madcap2.tricolour.ca> (raw)
In-Reply-To: <1718091.jpvVH885I0@x2>

On 14/01/14, Steve Grubb wrote:
> On Tuesday, January 14, 2014 01:09:52 PM Aaron Lewis wrote:
> > Yes, I did run auditctl -D to clear all rules. And during testing I
> > have enlarged the buffer queue to 10240 messages.
> > 
> > Did you mean that once -D is issued, the buffer will be cleared by
> > auditd, but not by linux kernel?
> 
> There is no way to directly clear the in kernel buffer. The audit system is 
> supposed to keep events for disposition. If there was a simple command to dump 
> events, that would be a simple way to circumvent detection. So, the best way 
> to drain the queues is to give auditd more priority so it runs more often and 
> longer before its time slice is up. You don't need to log to disk. But 
> something has to read the events to get them out.

What Steve said.

The -D option has nothing directly to do with the queue.  It simply
shuts off most of the the taps filling your sink.  You still need to
drain the sink after it has filled/overflowed.

> -Steve

- RGB

--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat
Remote, Ottawa, Canada
Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545

      reply	other threads:[~2014-01-14 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26  0:54 Clear kernel audit buffer? Aaron Lewis
2014-01-13 19:24 ` Richard Guy Briggs
2014-01-14  5:09   ` Aaron Lewis
2014-01-14 14:21     ` Steve Grubb
2014-01-14 14:47       ` Richard Guy Briggs [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=20140114144715.GQ13431@madcap2.tricolour.ca \
    --to=rgb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=sgrubb@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