linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: SELinux policy reload cannot be sent to audit system
Date: Thu, 05 Nov 2015 08:20:15 -0500	[thread overview]
Message-ID: <1545408.jriTJxqJyO@x2> (raw)
In-Reply-To: <563B20B9.6050209@debian.org>

On Thursday, November 05, 2015 10:26:17 AM Laurent Bigonville wrote:
> Le 05/11/15 09:32, Laurent Bigonville a écrit :
> > Le 05/11/15 04:23, Steve Grubb a écrit :
> >> I tested this on Fedora 22 and did not get a USER_AVC from dbus, but
> >> I also did not get an error message in syslog. So, I don't know what to
> >> make of it.
> >> (And for the record, I have a bz open saying that USER_AVC is the
> >> wrong event type. They are blaming libselinux but I blame them for not
> >> using AUDIT_USER_MAC_POLICY_LOAD.)
> > 
> > The audit code in dbus has been refactored a bit in the version
> > present F23 and debian unstable, so it might be related to this that.
> > 
> > Do you still have the number of that bz bug?
> 
> BTW, systemd is also apparently sending a USER_AVC event when the policy
> is reloaded.

This is bz 1195330.

-Steve

  reply	other threads:[~2015-11-05 13:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 16:05 SELinux policy reload cannot be sent to audit system Laurent Bigonville
2015-11-03 16:28 ` Steve Grubb
2015-11-03 16:38   ` Paul Moore
2015-11-03 17:12   ` Laurent Bigonville
2015-11-03 19:33     ` Steve Grubb
2015-11-03 20:08       ` Richard Guy Briggs
2015-11-03 20:48         ` Laurent Bigonville
2015-11-05  3:23           ` Steve Grubb
2015-11-05  8:32             ` Laurent Bigonville
2015-11-05  9:26               ` Laurent Bigonville
2015-11-05 13:20                 ` Steve Grubb [this message]
2015-11-05 23:03               ` Steve Grubb
2015-11-05 23:19                 ` Laurent Bigonville
2015-11-06  1:25                   ` Paul Moore

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=1545408.jriTJxqJyO@x2 \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.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).