Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Linux Audit <linux-audit@redhat.com>
Subject: audit 2.8.2 released
Date: Thu, 14 Dec 2017 13:07:42 -0500	[thread overview]
Message-ID: <1977264.EQ9jfnC5VH@x2> (raw)

Hello,

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:

- Update tables for 4.14 kernel
- Fixup ipv6 server side binding
- AVC report from aureport was missing result column header (#1511606)
- Add SOFTWARE_UPDATE event
- In ausearch/report pickup any path and new-disk fields as a file
- Fix value returned by auditctl --reset-lost (Richard Guy Briggs)
- In auparse, fix expr_create_timestamp_comparison_ex to be numeric field
- Fix building on old systems without linux/fanotify.h
- Fix shell portability issues reported by shellcheck
- Auditd validate_email should not use gethostbyname

This is a bug fix release that corrects several things in the 2.8 series. IPv6 
support was not binding to an IPv6 socket on the server side. auditctl --
reset-lost is intended to return the current value of the lost events value. 
It was returning the netlink sequence number. This is now corrected. The new 
ausearch test suite detected a bug in auparse_search functions that was 
introdiced in 2.8, the date was not considered a numeric field and thus could 
not match dates. This is fixed. It was also discovered that on older systems 
without fanotify.h, the build would fail. And lastly, validate_email was using 
gethostby name which validated against IPv4 addresses which is wrong given 
that IPv6 support was introduced. This has also been fixed.

SHA256: 67b59b2b77afee9ed87afa4d80ffc8e6f3a1f4bbedd5f2871f387c952147bcba

Please let me know if you run across any problems with this release.

-Steve

                 reply	other threads:[~2017-12-14 18:07 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=1977264.EQ9jfnC5VH@x2 \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox