From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: [PATCH] [AUDIT] Fix ANOM_PROMISCUOUS message format
Date: Thu, 10 Jan 2008 12:49:40 -0500 [thread overview]
Message-ID: <200801101249.40843.sgrubb@redhat.com> (raw)
In-Reply-To: <200801101241.00467.sgrubb@redhat.com>
On Thursday 10 January 2008 12:41:00 Steve Grubb wrote:
> And add a field at the end "res=1" since this doesn't appear to be able to
> fail.
Actually, I don't think this one is needed since its an ANOM event. They
should be true always. I guess we just need a test of audit_enabled added.
Thanks,
-Steve
next prev parent reply other threads:[~2008-01-10 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 17:25 [PATCH] [AUDIT] Fix ANOM_PROMISCUOUS message format Klaus Heinrich Kiwi
2008-01-10 17:41 ` Steve Grubb
2008-01-10 17:49 ` Steve Grubb [this message]
2008-01-10 17:58 ` Klaus Heinrich Kiwi
2008-01-10 18:22 ` Steve Grubb
2008-01-10 19:44 ` [PATCH v2] [AUDIT] Add uid, gid fields to ANOM_PROMISCUOUS message Klaus Heinrich Kiwi
2008-01-10 20:05 ` Eric Paris
2008-01-10 18:07 ` [PATCH] [AUDIT] Fix ANOM_PROMISCUOUS message format Eric Paris
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=200801101249.40843.sgrubb@redhat.com \
--to=sgrubb@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