From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Valdis.Kletnieks@vt.edu
Subject: Re: [PATCH] execve argument logging
Date: Fri, 21 Apr 2006 19:44:55 -0400 [thread overview]
Message-ID: <200604211944.56052.sgrubb@redhat.com> (raw)
In-Reply-To: <200604212122.k3LLMhMG018407@turing-police.cc.vt.edu>
On Friday 21 April 2006 17:22, Valdis.Kletnieks@vt.edu wrote:
> which implies to me that I can blat a bit over 128K to the audit log per
> syscall.
Users can do this already. Maybe not as quickly, but they can certainly fill
up your logs if they feel like it. If you do not want this message type in
your logs, then use this in your audit rules:
-a always,exclude -F msgtype=EXECVE
Problem Solved (tm).
-Steve
next prev parent reply other threads:[~2006-04-21 23:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 11:33 [PATCH] execve argument logging Alexander Viro
2006-04-21 13:20 ` Steve Grubb
2006-04-21 20:19 ` Valdis.Kletnieks
2006-04-21 20:22 ` Alexander Viro
2006-04-21 21:22 ` Valdis.Kletnieks
2006-04-21 23:44 ` Steve Grubb [this message]
2006-04-22 1:05 ` Valdis.Kletnieks
2006-04-21 20:23 ` 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=200604211944.56052.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--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