All of lore.kernel.org
 help / color / mirror / Atom feed
From: LC Bruzenak <lenny@magitekltd.com>
To: Linux Audit <linux-audit@redhat.com>
Subject: Re: audit-viewer "comm" question
Date: Mon, 04 Aug 2008 18:01:43 -0500	[thread overview]
Message-ID: <1217890903.30693.423.camel@homeserver> (raw)
In-Reply-To: <1217890182.30693.417.camel@homeserver>

On Mon, 2008-08-04 at 17:49 -0500, LC Bruzenak wrote:
> After reading Steve's info about the "comm" field being clipped at 16
> chars, I was surprised to see a longer string inside the audit-viewer
> "comm" field.
> I have taken a screen shot, but won't post it unless asked (it's 41K).
> The "comm" field there is: "/usr/libexec/gnome-settings-daemon", which
> of course is longer than 16 chars.
> 
> The same event in ausearch shows a NULL "comm" field, but the rest of
> the info lines up with the GUI:
> 
> [root@hugo ~]# ausearch -ts today -i -a 126492
> ----
> type=USER_AVC msg=audit(08/04/2008 16:04:24.152:126492) : user pid=23501
> uid=root auid=unset subj=system_u:system_r:xdm_xserver_t:s0-s15:c0.c1023
> msg='avc:  denied  { receive } for  comm=(null) event=X11:PropertyNotify
> scontext=user_u:user_r:user_t:s0-s15:c0.c1023
> tcontext=user_u:object_r:property_xevent_t:s4:c0,c2,c11,c200.c511
> tclass=x_event : exe=/usr/bin/Xorg (sauid=root  hostname=?, addr=?,
> terminal=?)' 
> 

I guess the question here is not why there is > 16 chars (since this is
a USER_AVC not kernel-generated event - right?) but rather why the GUI
shows the comm but the ausearch doesn't.
 
Thx,
LCB.

-- 
LC (Lenny) Bruzenak
lenny@magitekltd.com

  reply	other threads:[~2008-08-04 23:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 22:49 audit-viewer "comm" question LC Bruzenak
2008-08-04 23:01 ` LC Bruzenak [this message]
2008-08-04 23:15   ` Steve Grubb
2008-08-04 23:11 ` Steve Grubb

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=1217890903.30693.423.camel@homeserver \
    --to=lenny@magitekltd.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 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.