From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: audit@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] audit/audit-pr-20250527
Date: Tue, 27 May 2025 18:57:45 -0400 [thread overview]
Message-ID: <2d7b064b34bcff7a6a8926cc29cae659@paul-moore.com> (raw)
Linus,
Two audit patches for the Linux v6.16 merge window:
- Always record AUDIT_ANOM events when auditing is enabled.
Prior to this patch we only recorded AUDIT_ANOM events if auditing was
enabled and the admin/distro had explicitly configured audit beyond the
defaults. Considering that AUDIT_ANOM events are anomolous events
considered to be "security relevant", it seems wise to record these
events as long as auditing is enabled, even if the system is running
with a default audit configuration.
- Mark the audit_log_vformat() function with the __printf() attribute
to quiet GCC.
Paul
--
The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:
Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git
tags/audit-pr-20250527
for you to fetch changes up to 654d61b8e0e2f8b9bdea28a9a51279ecdacafe3c:
audit: record AUDIT_ANOM_* events regardless of presence of rules
(2025-04-11 14:14:41 -0400)
----------------------------------------------------------------
audit-pr-20250527
----------------------------------------------------------------
Andy Shevchenko (1):
audit: mark audit_log_vformat() with __printf() attribute
Richard Guy Briggs (1):
audit: record AUDIT_ANOM_* events regardless of presence of rules
kernel/audit.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
paul-moore.com
next reply other threads:[~2025-05-27 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 22:57 Paul Moore [this message]
2025-05-28 15:42 ` [GIT PULL] audit/audit-pr-20250527 pr-tracker-bot
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=2d7b064b34bcff7a6a8926cc29cae659@paul-moore.com \
--to=paul@paul-moore.com \
--cc=audit@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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