public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: zhangxiliang <zhangxiliang@cn.fujitsu.com>
Cc: audit-list <linux-audit@redhat.com>
Subject: Re: [graphics 06448] [PATCH 2/2] fix a bug that use option '-k key-string' cannot search out all matched logs
Date: Wed, 30 Jul 2008 07:06:19 -0400	[thread overview]
Message-ID: <200807300706.19593.sgrubb@redhat.com> (raw)
In-Reply-To: <488FC4D9.5030804@cn.fujitsu.com>

On Tuesday 29 July 2008 21:33:13 zhangxiliang wrote:
> > echo 'node=RHEL5.2GA type=CONFIG_CHANGE msg=audit(1217404709.683:23182):
> > auid=0 subj=root:system_r:auditctl_t:s0-s0:c0.c1023 op=remove rule
> > key="haha" list=4 res=1'
>
> Why the message which type is "CONFIG_CHANGE" contains "key" field?
> The "CONFIG_CHANGE" audit message should only describe the audit object
> status.

The reason that the key field is output is an attempt at telling the security 
officer more about which rule was deleted. Yes at the commandline you know 
what rules you just deleted, but if all you have is the logs and it happened 
some time in the past, how do you know *exactly* which rule was deleted? This 
gets us closer without having to write something in the kernel that iterates 
through the fields and changes them to text. We really can't do that in the 
kernel.

-Steve

  reply	other threads:[~2008-07-30 11:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  5:41 [PATCH 2/2] fix a bug that use option '-k key-string' cannot search out all matched logs Peng Haitao
2008-07-29 21:22 ` Steve Grubb
2008-07-30  1:33 ` [graphics 06448] " zhangxiliang
2008-07-30 11:06   ` Steve Grubb [this message]
2008-07-31  9:16     ` zhangxiliang

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=200807300706.19593.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=zhangxiliang@cn.fujitsu.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