From: Steve Grubb <sgrubb@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] execve argument logging
Date: Fri, 21 Apr 2006 16:23:39 -0400 [thread overview]
Message-ID: <200604211623.39536.sgrubb@redhat.com> (raw)
In-Reply-To: <200604212019.k3LKJ9jr015983@turing-police.cc.vt.edu>
On Friday 21 April 2006 16:19, Valdis.Kletnieks@vt.edu wrote:
> Does this allow an attacker to DoS the audit log by creating a fork/exec
> loop intentionally invoking a totally duff binary, but that includes a very
> long argument?
I personally haven't tried. Try it and let us know if you can DoS the machine.
> Maybe a "first 32/64 bytes of each argument" limit is needed? Or is there
> one there and I missed it?
There's no limit other than what the kernel imposes.
-Steve
prev parent reply other threads:[~2006-04-21 20:23 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
2006-04-22 1:05 ` Valdis.Kletnieks
2006-04-21 20:23 ` Steve Grubb [this message]
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=200604211623.39536.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