From: Steve Grubb <sgrubb@redhat.com>
To: Linux Audit <linux-audit@redhat.com>
Subject: audit-2.0.1 released
Date: Mon, 28 Sep 2009 16:32:35 -0400 [thread overview]
Message-ID: <200909281632.35232.sgrubb@redhat.com> (raw)
Hi,
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:
- Aulast now reads daemon_start events for the kernel version of reboot
- Clarify the man pages for ausearch/report regarding locale and date formats
- Fix getloginuid for python bindings
- Disable the audispd af_unix plugin by default
- Add a couple new init script actions for LSB 3.2
- In audisp-remote plugin, timeout network reads (#514090)
- Make some error logging in audisp-remote plugin more prominent
- Add audit.rules man page
- Interpret the session field in audit events
This is mostly a bug fix release. It was noticed in aulast that all the
kernel's being printed were the same. Now we extract that information from
DAEMON_START events which records the uname info.
The python bindings for getloginuid made an error on the uid_t data type.
Ausearch now interprets ses=-1 to unset.
The af_unix plugin was enabled by default since setroubleshooter was acting as
a standalone daemon. It has been starting off of audispd for a while, so now
there should be no known applications needing af_unix.
The initscripts were not 100% LSB 3.2 compliant. They should be now.
In some situations, the audisp-remote plugin was not timing out fast enough on
some network errors. This has been fixed.
And in the interest in helping people write audit rules, a new man page
"audit.rules" has been added with a very long explanation of a lot of issues.
Please let me know if you run across any problems with this release.
-Steve
PS - there will a release in the 1.7 branch soon rolling up a lot of bug fixes
from the trunk.
reply other threads:[~2009-09-28 20:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200909281632.35232.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.