I've just released a new version of the audit daemon. It can be downloaded from http://people.redhat.com/sgrubb/audit. It will also be in rawhide soon. The ChangeLog is: - Add an option to auditctl to interpret a0 - a3 of syscall rules when listing - Improve ARM and AARCH64 support (AKASHI Takahiro) - Add ausearch --checkpoint feature (Burn Alting) - Add --arch option to ausearch - Improve too long config line in audispd, auditd, and auparse (#1071580) - Fix aulast to accept the new AUDIT_LOGIN record format - Remove clear_config symbol in auparse I decided to go ahead and release this one because of some concern about an unintended symbol popping up in the auparse ABI. This release include a bunch of new stuff. You can now add a '-i' to the listing command of auditctl and it will interpret a0-a3 if they are included in any rules. There is new support for arm as mentioned in an email a few weeks ago. If you were compiling --with-armeb, you now need to change to --with-arm. Cross compile support is not yet in place. There is a new checkpoint feature to ausearch. What it does is give you all the events that have occurred since the last checkpoint. Ausearch now has a --arch search option just in case you needed to find i386 events on a x86_64 machine. There were a number of cleanups to the code as well. Please let me know if you run across any problems with this release. -Steve -- Linux-audit mailing list Linux-audit(a)redhat.com https://www.redhat.com/mailman/listinfo/linux-audit

On Sunday, April 13, 2014 11:51:45 AM Burn Alting wrote: > A patch is attached that addresses this. > > Essentially the modification > - notices if we identify an audit.log file to use but we do not find the > recorded audit event in that log file and so report an error (to stderr) > and return a new exit code (12) > - allows checkpointing to only use the recorded time from the checkpoint > file for comparisons. I'd like to look at these two pieces separately. Let's have 1 bug/feature per patch. This way if something looks good, it can be applied immediately. Whereas if something needs more discussion, it would block application of the part that is good. > You will note that the patch also contains changes to swig/audit.py. > Although this file is automatically generated, it is part of the 2.3.6 > release ... should it be? I suppose it should be. What is in the release is decided by automake/autoconf. If there are any mistakes in the Makefile.am file, I would take a patch. > I also note that a lot of Makefile.in's are also part of the release. Again, > should these automatically generated files be part of the release? The audit package release is done by a script that pretty much does the following (its way more complicated than this, but this is the essential pieces): mkdir audit cd audit svn co http://svn.fedorahosted.org/svn/audit/trunk . ./autogen.sh ./configure make -j 8 distcheck If it finishes saying it created the tar ball, I send it to rawhide to make sure it builds on a current OS. If that is also successful, then I push it to my people page and then commit a branch in svn. I also run the development audit package on all my systems during the whole development cycle to make sure bugs are fixed, nothing new shows up, and its builds under normal conditions. So, anything that is there, is because autotools think it should be there unless I made a mistake in a Makefile.am. :-) Patches are welcome. Thanks, -Steve

On Sunday, April 13, 2014 11:51:45 AM Burn Alting wrote: > A patch is attached that addresses this. > > Essentially the modification > - notices if we identify an audit.log file to use but we do not find the > recorded audit event in that log file and so report an error (to stderr) > and return a new exit code (12) > - allows checkpointing to only use the recorded time from the checkpoint > file for comparisons. I'd like to look at these two pieces separately. Let's have 1 bug/feature per patch. This way if something looks good, it can be applied immediately. Whereas if something needs more discussion, it would block application of the part that is good. > You will note that the patch also contains changes to swig/audit.py. > Although this file is automatically generated, it is part of the 2.3.6 > release ... should it be? I suppose it should be. What is in the release is decided by automake/autoconf. If there are any mistakes in the Makefile.am file, I would take a patch. > I also note that a lot of Makefile.in's are also part of the release. Again, > should these automatically generated files be part of the release? The audit package release is done by a script that pretty much does the following (its way more complicated than this, but this is the essential pieces): mkdir audit cd audit svn co http://svn.fedorahosted.org/svn/audit/trunk . ./autogen.sh ./configure make -j 8 distcheck If it finishes saying it created the tar ball, I send it to rawhide to make sure it builds on a current OS. If that is also successful, then I push it to my people page and then commit a branch in svn. I also run the development audit package on all my systems during the whole development cycle to make sure bugs are fixed, nothing new shows up, and its builds under normal conditions. So, anything that is there, is because autotools think it should be there unless I made a mistake in a Makefile.am. :-) Patches are welcome. Thanks, -Steve