On Tue, 2008-03-04 at 15:29 -0500, John Dennis wrote:
Steve Grubb wrote:
> If there's no agreement with them, should we change anything?
> auparse is working pretty good as is.
No it's not. The auparse approach is based on tables, tables which have
been shown to be incorrect and tied to kernel versions and the patch set
used to build that kernel version. Like it or not, audit data is and
will be divorced from kernel versions. In fact audit data will derive
from a mix of different kernel versions if the audit data is aggregated,
which is the plan. In the current scheme there is no realistic way to
process audit data from thousands of nodes all running different kernels
in an enterprise wide auditing system.
Any scheme which requires knowing the kernel version and patch set to
correctly read the data is broken. Attempts to cast this issue as
pandering to userspace weenies is off the mark by a mile.
But even if the messages
were parsable into a tree regardless of kernel
version, for semantic understanding of the messages you'll still have to
know which kernel generated them unless the semantics is set in stone
for all possible messages.
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb