From: Paul Moore <paul@paul-moore.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
"Jérémie Galarneau" <jeremie.galarneau@efficios.com>,
s.mesoraca16@gmail.com, viro@zeniv.linux.org.uk,
dan.carpenter@oracle.com, akpm@linux-foundation.org,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
kernel-hardening@lists.openwall.com, linux-audit@redhat.com,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [PATCH v3] audit: Report suspicious O_CREAT usage
Date: Thu, 3 Oct 2019 14:29:17 -0400 [thread overview]
Message-ID: <CAHC9VhQKyHAvNhuquVEYXP9U7ix2pDwXGnRO6QaxYTUKA08=UQ@mail.gmail.com> (raw)
In-Reply-To: <201910021640.B01FA41@keescook>
On Wed, Oct 2, 2019 at 7:42 PM Kees Cook <keescook@chromium.org> wrote:
>
> This renames the very specific audit_log_link_denied() to
> audit_log_path_denied() and adds the AUDIT_* type as an argument. This
> allows for the creation of the new AUDIT_ANOM_CREAT that can be used to
> report the fifo/regular file creation restrictions that were introduced
> in commit 30aba6656f61 ("namei: allow restricted O_CREAT of FIFOs and
> regular files").
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> v3:
> - retain existing operation names (paul)
> v2:
> - fix build failure typo in CONFIG_AUDIT=n case
> - improve operations naming (paul)
> ---
> fs/namei.c | 8 ++++++--
> include/linux/audit.h | 5 +++--
> include/uapi/linux/audit.h | 1 +
> kernel/audit.c | 11 ++++++-----
> 4 files changed, 16 insertions(+), 9 deletions(-)
Merged into audit/next - thanks!
--
paul moore
www.paul-moore.com
prev parent reply other threads:[~2019-10-03 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 23:41 [PATCH v3] audit: Report suspicious O_CREAT usage Kees Cook
2019-10-03 18:29 ` Paul Moore [this message]
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='CAHC9VhQKyHAvNhuquVEYXP9U7ix2pDwXGnRO6QaxYTUKA08=UQ@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=jeremie.galarneau@efficios.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=s.mesoraca16@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).