From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: Dominick Grift <domg472@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: XACE: tclass malformed
Date: Thu, 17 Sep 2009 17:02:48 -0400 [thread overview]
Message-ID: <4AB2A3F8.6090301@tycho.nsa.gov> (raw)
In-Reply-To: <20090910203602.GB6469@notebook3.grift.internal>
On 09/10/2009 04:36 PM, Dominick Grift wrote:
> On Thu, Sep 10, 2009 at 04:29:07PM -0400, Eamon Walsh wrote:
>
>> On 09/10/2009 12:03 PM, Dominick Grift wrote:
>>
>>> Some XACE avc denials end up in /var/log/messages as opposed to /var/log/audit/audit.log. These particular XACE avc denials appear with a malformed tclass field:
>>>
>>> Example:
>>>
>>> Sep 10 17:50:31 notebook3 Xephyr: Can't send to audit system: USER_AVC avc: denied { get_property } for request=X11:GetProperty comm=/usr/bin/xterm resid=102 restype=WINDOW scontext=dgrift_u:dgrift_r:sandbox_x_client_t:s0:c29,c36 tcontext=dgrift_u:object_r:sandbox_xserver_t:s0:c29,c36 tclass=x_drawable#012: exe="/usr/bin/Xephyr" sauid=0 hostname=? addr=? terminal=?
>>>
>>> note the: tclass=x_drawable#012:
>>>
>>> I believe this may be the reason why these avc denials end up in /var/log/messages instead of /var/log/audit/audit.log , but i am not sure.
>>>
>>>
I'm seeing malformed messages in /var/log/messages (with the #012) that
have nothing to do with XACE. So I think this is an audit bug.
--
Eamon Walsh<ewalsh@tycho.nsa.gov>
National Security Agency
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2009-09-17 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 16:03 XACE: tclass malformed Dominick Grift
2009-09-10 20:29 ` Eamon Walsh
2009-09-10 20:36 ` Dominick Grift
2009-09-17 21:02 ` Eamon Walsh [this message]
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=4AB2A3F8.6090301@tycho.nsa.gov \
--to=ewalsh@tycho.nsa.gov \
--cc=domg472@gmail.com \
--cc=selinux@tycho.nsa.gov \
/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.