From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: aureport summary
Date: Wed, 28 May 2008 19:42:50 -0400 [thread overview]
Message-ID: <200805281942.51135.sgrubb@redhat.com> (raw)
In-Reply-To: <1212017265.6610.56.camel@homeserver>
On Wednesday 28 May 2008 19:27:45 LC Bruzenak wrote:
> IIUC the last line - number of events - should be the sum of all the
> previous.
> However, adding up the events (barring OE) before that comes to 23791. I
> guess there are overlaps too - for example, the keys are possibly also
> in syscall events?
> Are some events missing on purpose?
Yes. Not every event falls into a category mentioned above. For example, on
login you have USER_ACCT and CRED_ACQ, both of which are not picked off and
highlighted. Just the USER_AUTH and USER_START get counted. There are others
like that all over.
So, the short answer is that there are no guarantees that they all add up and
yes there can be overlaps.
-Steve
prev parent reply other threads:[~2008-05-28 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 23:27 aureport summary LC Bruzenak
2008-05-28 23:42 ` 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=200805281942.51135.sgrubb@redhat.com \
--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