From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com, Paul Moore <paul@paul-moore.com>
Subject: Re: Be careful with rules
Date: Tue, 07 Jun 2022 11:02:08 -0400 [thread overview]
Message-ID: <11997104.O9o76ZdvQC@x2> (raw)
In-Reply-To: <CAHC9VhTnkKDtMAH1_Yz5HMsCHCuj3p9V5RzfrpW84wpNPLXjPw@mail.gmail.com>
Hello Paul,
On Tuesday, June 7, 2022 9:42:06 AM EDT Paul Moore wrote:
> On Mon, Jun 6, 2022 at 7:10 PM Lenny Bruzenak <lenny@magitekltd.com> wrote:
> > I've been told that it is not a potential security problem, and not
> > subject to change in the (current) kernel.
>
> I'm that little birdy that Lenny was talking to off-list so I figured
> I would add a quick comment here :)
>
> As a reminder, elevated privilege is needed to both add/remove/modify
> audit rules as well as the loaded SELinux policy (affecting the
> validity of the relevant security labels). Also, as Lenny already
> mentioned, if an invalid security label is used, the kernel will
> notify the admin via the kernel log.
Wouldn't it be better if the kernel knew the rule was invalid to return
EINVAL so that rule loading stops or becomes an error return from auditctl? A
long time ago, there was no way from user space to check a type or a role or
an selinux user for validity. Can that be done now? Is there an API for it?
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2022-06-07 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 23:09 Be careful with rules Lenny Bruzenak
2022-06-07 13:42 ` Paul Moore
2022-06-07 15:02 ` Steve Grubb [this message]
2022-06-07 15:14 ` Paul Moore
2022-06-07 16:35 ` Lenny Bruzenak
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=11997104.O9o76ZdvQC@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=paul@paul-moore.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.