public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: John Dennis <jdennis@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: 'linux-audit' <linux-audit@redhat.com>
Subject: Re: [Patch]Fix the error in the output of "auditctl -s" when	auditd is stoped
Date: Thu, 07 Aug 2008 09:55:20 -0400	[thread overview]
Message-ID: <489AFEC8.6070907@redhat.com> (raw)
In-Reply-To: <1218116377.5837.67.camel@localhost.localdomain>


[-- Attachment #1.1: Type: text/plain, Size: 1086 bytes --]

Eric Paris wrote:
> On Thu, 2008-08-07 at 12:50 +0800, Chu Li wrote:
>   
>> Hi Steve,
>>   When auditd is stoped, "auditctl -s" will show "pid=0". I think it's not
>> correct information. It's better to tell users "auditd not started".
>>     
>
> We do try to keep the whole key=value pair thing in audit records.  I'd
> be willing to go with something like -1 to make it really clear, but
> with the number of complaints about the inconsistencies of audit records
> from people like John Dennis I'm not sure I'm a fan of this patch....
>   
Thank you Eric! We should be moving toward consistent formatting of 
audit records and one of the most important consistencies to achieve if 
we do modify the records is that all data is in the form of key=value. 
Embedding random strings into records makes parsing difficult especially 
when the record format varies by kernel version, which this patch would 
do (at least the proposed string didn't contain any embedded spaces!)

NAK to this patch.

I think Eric's suggestion of pid=-1 is a good one.

-- 
John Dennis <jdennis@redhat.com>


[-- Attachment #1.2: Type: text/html, Size: 1639 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2008-08-07 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07  4:50 [Patch]Fix the error in the output of "auditctl -s" when auditd is stoped Chu Li
2008-08-07 13:39 ` Eric Paris
2008-08-07 13:54   ` Steve Grubb
2008-08-07 13:55   ` John Dennis [this message]
2008-08-07 21:01 ` Steve Grubb
2008-08-08  1:10   ` Chu Li

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=489AFEC8.6070907@redhat.com \
    --to=jdennis@redhat.com \
    --cc=eparis@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