Mirek,
After applying this patch my build fails in the parse test section due
to a difference of no space after a comma:
diff -u ../../auparse/test/auparse_test.ref auparse_test.cur
--- ../../auparse/test/auparse_test.ref 2009-02-24 15:11:35.0
-0600
+++ auparse_test.cur2009-03-27
- LC Bruzenak le...@magitekltd.com wrote:
After applying this patch my build fails in the parse test section due
to a difference of no space after a comma:
-mode=040730 (dir, 730)
+mode=040730 (dir,730)
Do you think your changes would cause this?
Yes, that change was
On Fri, 2009-03-27 at 10:44 -0500, LC Bruzenak wrote:
Mirek,
After applying this patch my build fails in the parse test section due
to a difference of no space after a comma:
diff -u ../../auparse/test/auparse_test.ref auparse_test.cur
--- ../../auparse/test/auparse_test.ref 2009-02-24
Hello all,
I have just run into the problem that many of you have: trying to parse
the audit logs.
Yesterday I read through the linux-audit mail archive. Here are the
related topics I have found:
https://www.redhat.com/archives/linux-audit/2006-March/msg00093.html
Joshua Roys wrote:
Hello all,
I have just run into the problem that many of you have: trying to
parse the audit logs.
Based on things other people have proposed, how does this sound:
- hex-encode strings (and do not quote) if:
-- contains non-ASCII or non-printable characters
- quote strings
etienne wrote:
Hi,
could you have a look at this patch from the audit point of view?
thanks,
Etienne
Hello,
the following patch, against current 2.6.29-rc7, add logging of smack
decisions.
This is of course very useful to understand what your current smack policy
does.
It
