From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: Mike Palmiotto <mike.palmiotto@crunchydata.com>
Cc: SElinux list <selinux@vger.kernel.org>
Subject: Re: [PATCH] libselinux: Use sestatus if open
Date: Thu, 16 Jul 2020 08:39:49 -0400 [thread overview]
Message-ID: <CAEjxPJ6PQe0WPOA-LjNbfhRfDP7=dJ7N0aisCu9Y=WSHC7HXGA@mail.gmail.com> (raw)
In-Reply-To: <CAMN686H=3RY-E1a01fWPY9QqGpUABVxJmQGrx00c53JrMVswZA@mail.gmail.com>
On Wed, Jul 15, 2020 at 6:45 PM Mike Palmiotto
<mike.palmiotto@crunchydata.com> wrote:
> Interestingly, the test program is working fine:
> https://github.com/mpalmi/selinux/tree/sestatus
> https://github.com/mpalmi/sestatus-test
>
> On a test run, I'm seeing both the status page and netlink socket
> notifications for load_polcy (twice for each case):
>
> ```
> ./test
> opened avc successfully
> got netlink socket: 4
>
> watching netlink socket for events
> avc: received policyload notice (seqno=3)
> policy reload notice received
> avc: received policyload notice (seqno=4)
> policy reload notice received
> ^C
> watching sestatus page for events
> avc: received policyload notice (seqno=5)
> policy reload notice received
> avc: received policyload notice (seqno=6)
> policy reload notice received
> ^Cclosing netlink socket: 4
> destroying avc
> goodbye
> ```
>
> Still seeing the MAC_POLICY_LOAD audit message, but none of the usual
> USER_AVC policyload notices.
I only see one notification per load_policy invocation. What versions
of kernel and dbus are you using? Are you using dbus-daemon or
dbus-broker? How are you testing dbus with this change - just doing a
make install relabel of libselinux and restarting dbus-daemon or
dbus-broker, then running load_policy and checking for USER_AVC
messages? Is this on CentOS 7/8?
next prev parent reply other threads:[~2020-07-16 12:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 20:29 [PATCH] libselinux: Use sestatus if open Mike Palmiotto
2020-07-14 20:29 ` Mike Palmiotto
2020-07-14 21:03 ` Stephen Smalley
2020-07-14 21:20 ` Mike Palmiotto
2020-07-14 21:35 ` Stephen Smalley
2020-07-14 22:42 ` Mike Palmiotto
2020-07-15 16:04 ` Mike Palmiotto
2020-07-15 16:49 ` Stephen Smalley
2020-07-15 17:10 ` Mike Palmiotto
2020-07-15 18:52 ` Mike Palmiotto
2020-07-15 19:49 ` Stephen Smalley
2020-07-15 22:45 ` Mike Palmiotto
2020-07-16 12:39 ` Stephen Smalley [this message]
2020-07-16 13:36 ` Mike Palmiotto
2020-07-16 15:12 ` Stephen Smalley
2020-07-16 15:27 ` Stephen Smalley
2020-07-16 15:44 ` Mike Palmiotto
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='CAEjxPJ6PQe0WPOA-LjNbfhRfDP7=dJ7N0aisCu9Y=WSHC7HXGA@mail.gmail.com' \
--to=stephen.smalley.work@gmail.com \
--cc=mike.palmiotto@crunchydata.com \
--cc=selinux@vger.kernel.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 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.