From: Dominick Grift <dac.override@gmail.com>
To: Ted Toth <txtoth@gmail.com>
Cc: selinux@vger.kernel.org
Subject: Re: RHEL auth_role using logging_send_audit_msgs
Date: Wed, 27 Feb 2019 09:21:07 +0100 [thread overview]
Message-ID: <20190227082107.GA17179@brutus.lan> (raw)
In-Reply-To: <CAFPpqQEHRb5pW7HGx7-yZgBbneA3US_nb4HqRAG5uSkYbxg+Jw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Tue, Feb 26, 2019 at 04:20:42PM -0600, Ted Toth wrote:
> The RHEL version of the auth_role macro which we are getting through
> our use of userdom_unpriv_user_template uses logging_send_audit_msgs
> which give a type the audit_write capability and allow rules for a
> number of netlink_audit_socket operations. It seem counterintuitive to
> give an unprivileged user type audit write related policy.The
> ref-policy version of auth_role does not use logging_send_audit_msgs.
> We're considering patching our policy but I wanted to see what others
> though about giving unprivileged user types this policy?
>
> Ted
I think this should indeed probably be dontaudited (i have a few of those in my policy as well, so do as i say not as i do)
Might have been added because of some unpriviliged user space object manager trying to log to audit. These would not have been allowed anyway.
XSELinux, old dbus come to mind.
--
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2019-02-27 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 22:20 RHEL auth_role using logging_send_audit_msgs Ted Toth
2019-02-27 8:21 ` Dominick Grift [this message]
2019-02-27 9:39 ` Dominick Grift
2019-02-27 13:07 ` Stephen Smalley
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=20190227082107.GA17179@brutus.lan \
--to=dac.override@gmail.com \
--cc=selinux@vger.kernel.org \
--cc=txtoth@gmail.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;
as well as URLs for NNTP newsgroup(s).