From: Ted Toth <txtoth@gmail.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@vger.kernel.org
Subject: Re: strange tclass in AVCs
Date: Wed, 18 Sep 2019 09:03:23 -0500 [thread overview]
Message-ID: <CAFPpqQGfAifnShcWTMs1pJe1m7W_4wM8AUqFsvj4Zts5-9QiCQ@mail.gmail.com> (raw)
In-Reply-To: <ac6433e2-88a4-747c-66f5-d241499f40d6@tycho.nsa.gov>
On Wed, Sep 18, 2019 at 8:53 AM Stephen Smalley <sds@tycho.nsa.gov> wrote:
>
> On 9/18/19 9:35 AM, Ted Toth wrote:
> > I'm seeing things like tclass=context#012 in some AVCs what is this telling me?
>
> Just a guess here, but octal 012 is '\n' aka a newline character, and
> libselinux/src/avc.c:avc_audit() appends a "\n" at the end of the buffer
> before calling avc_log() to log the entire string. avc_log() will call
> the logging callback, and dbusd does define one, which calls
> audit_log_user_avc_message(). Maybe audit_log_user_avc_message() is
> escaping the newline character in its output as well as appending
> additional data.
>
> I'm a little unclear though on why dbusd is checking a context contains
> permission?
These appear to only occur when systemd is starting the dbus daemon
and they end up in /var/log/messages not /var/log/audit/audit.log as
I'd expect.
next prev parent reply other threads:[~2019-09-18 14:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 13:35 strange tclass in AVCs Ted Toth
2019-09-18 13:46 ` Dominick Grift
2019-09-18 13:49 ` Dominick Grift
2019-09-18 13:51 ` Ted Toth
2019-09-18 13:53 ` Stephen Smalley
2019-09-18 14:03 ` Ted Toth [this message]
2019-09-18 14:11 ` Ted Toth
2019-09-18 14:17 ` Stephen Smalley
2019-09-19 13:02 ` Ted Toth
2019-09-19 17:03 ` Stephen Smalley
2019-09-19 17:19 ` Ted Toth
2019-09-19 17:24 ` 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=CAFPpqQGfAifnShcWTMs1pJe1m7W_4wM8AUqFsvj4Zts5-9QiCQ@mail.gmail.com \
--to=txtoth@gmail.com \
--cc=sds@tycho.nsa.gov \
--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 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).