From: Steve Grubb <sgrubb@redhat.com>
To: Paul Moore <paul.moore@hp.com>
Cc: linux-audit@redhat.com
Subject: Re: audit 1.2.7 released
Date: Wed, 20 Sep 2006 15:40:52 -0400 [thread overview]
Message-ID: <200609201540.52990.sgrubb@redhat.com> (raw)
In-Reply-To: <451195CB.9000909@hp.com>
On Wednesday 20 September 2006 15:26, Paul Moore wrote:
> > I try very hard to not have any memory allocations in the audit system to
> > prevent any possible failure due to fragmentation or leaks. I need to cap
> > the buffer size at something to meet this design goal.
>
> If this buffer limitation results in the loss or partial-loss of an
> audit record is there some notification sent?
No.
> This seems like an excellent way for an individual to obscure their actions
> on a system.
Well, the particular buffer that Amy cited was 128 in size and only for
startup/shutdown messages. It has been increased to 384. The other buffer
that holds the events from syscall, file system, and trusted apps was 8460
and is now 8970.
-Steve
next prev parent reply other threads:[~2006-09-20 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 0:13 audit 1.2.7 released Steve Grubb
2006-09-19 21:05 ` Amy Griffis
2006-09-19 22:18 ` Steve Grubb
2006-09-20 19:12 ` Stephen Smalley
2006-09-20 19:19 ` Steve Grubb
2006-09-20 19:26 ` Paul Moore
2006-09-20 19:40 ` Steve Grubb [this message]
2006-09-21 19:43 ` Karl MacMillan
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=200609201540.52990.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=paul.moore@hp.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.