From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Grubb <sgrubb@redhat.com>
Subject: Re: [PATCH] execve argument logging
Date: Fri, 21 Apr 2006 16:23:39 -0400
Message-ID: <200604211623.39536.sgrubb@redhat.com>
References: <20060421113326.GA27648@devserv.devel.redhat.com>
	<200604210920.10253.sgrubb@redhat.com>
	<200604212019.k3LKJ9jr015983@turing-police.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Return-path: <linux-audit-bounces@redhat.com>
In-Reply-To: <200604212019.k3LKJ9jr015983@turing-police.cc.vt.edu>
Content-Disposition: inline
List-Unsubscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=subscribe>
Sender: linux-audit-bounces@redhat.com
Errors-To: linux-audit-bounces@redhat.com
To: Valdis.Kletnieks@vt.edu
Cc: linux-audit@redhat.com
List-Id: linux-audit@redhat.com

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/exe=
c
> 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 mac=
hine.

> Maybe a "first 32/64 bytes of each argument" limit is needed? =C2=A0Or =
is there
> one there and I missed it?

There's no limit other than what the kernel imposes.

-Steve