Finalize audit-4.0 release

ChangeLog

@@ -1,4 +1,4 @@
-3.9
+4.0
 - Drop python2 support
 - Drop auvirt and autrace programs
 - Drop SysVinit support

README.md

@@ -8,7 +8,6 @@ RUNTIME DEPENDENCIES
 * coreutils
 * initscripts-service
 * kernel >= 5.0 
-* procps-ng
 * systemd
 
 BUILD-TIME DEPENDENCIES
@@ -42,7 +41,7 @@ NOTE: **There is a moratorium on adding support for any new platforms.** Syscall
 
 MAIL LIST
 ---------
-The audit community has a [mail list](http://www.redhat.com/mailman/listinfo/linux-audit). It is the best place to ask questions because the mail archive is searchable and therefore discoverable.
+The audit community has a [mail list](https://lists.linux-audit.osci.io/archives/list/linux-audit@lists.linux-audit.osci.io/). It is the best place to ask questions because the mail archive is searchable and therefore discoverable.
 
 CONFIGURING AND COMPILING
 -------------------------
@@ -61,11 +60,7 @@ If you are packaging this, you probably want to do "make dist" instead and use t
 
 CROSS COMPILING
 ---------------
-Cross compiling is not supported. The audit system builds native binaries at
-build time and uses those to create sorted btrees for fast lookup during
-event processing and reporting. To enable cross compiling, those binaries
-would need to be rewritten in python or another scripting language. No one is
-currently working on that.
+Cross compiling is not officially supported. There have been people that have submitted patches to make it work. But it is not documented how to make it work. It is likely that you have to somehow override CC, CXX, RANLIB, AR, LD, and NM when running configure to pickup the cross compiler, linker, archive, etc.
 
 OVERVIEW
 --------
@@ -243,3 +238,7 @@ The auparse library is available to allow one to create custom reporting applica
 
 You can write programs in one of two ways: iterate across events, records, and fields; or use the feed API and to which a callback function is presented with a single, complete event that can be iterated across the records and fields. The former is best for working with files, while the latter is more appropriate for realtime data for a plugin.
 
+Audit Standards
+---------------
+You can find the standards to which the audit system conforms to in the ![Audit Documentation Project](https://github.com/linux-audit/audit-documentation).
+

TODO

@@ -1,7 +1,6 @@
 Future roadmap (subject to change):
 ===================================
-4.0
-* Rewrite swig based python
+4.0.x
 * In auditd, look into non-blocking handling of write to plugins
 * Basic HIDS based on reactive audit component
 * Multi-thread audisp-remote
@@ -15,3 +14,4 @@ Future roadmap (subject to change):
 
 Someday...
 * Container support
+* Rewrite swig based python

audit.spec

@@ -1,6 +1,6 @@
 Summary: User space tools for kernel auditing
 Name: audit
-Version: 3.9
+Version: 4.0
 Release: 1%{dist}
 License: GPL-2.0-or-later AND LGPL-2.0-or-later
 Group: System Environment/Daemons
@@ -267,6 +267,6 @@ fi
 %config(noreplace) %attr(640,root,root) /etc/audit/audit-stop.rules
 
 %changelog
-* Sun Aug 06 2023 Steve Grubb <[email protected]> 3.9-1
+* Tue Jan 16 2024 Steve Grubb <[email protected]> 4.0-1
 - New upstream release
 

configure.ac

@@ -2,7 +2,7 @@
 dnl
 define([AC_INIT_NOTICE],
 [### Generated automatically using autoconf version] AC_ACVERSION [
-### Copyright 2005-23 Steve Grubb <[email protected]>
+### Copyright 2005-24 Steve Grubb <[email protected]>
 ###
 ### Permission is hereby granted, free of charge, to any person obtaining a
 ### copy of this software and associated documentation files (the "Software"),
@@ -30,7 +30,7 @@ define([AC_INIT_NOTICE],
 ])
 
 AC_REVISION($Revision: 1.3 $)dnl
-AC_INIT([audit], [3.9])
+AC_INIT([audit], [4.0])
 AC_PREREQ([2.50])dnl
 AC_CONFIG_HEADERS([config.h])