From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: user message limits Date: Wed, 28 Jan 2009 12:15:16 -0500 Message-ID: <200901281215.16996.sgrubb@redhat.com> References: <1233100868.30154.103.camel@homeserver> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: Received: from vpn-12-26.rdu.redhat.com (vpn-12-26.rdu.redhat.com [10.11.12.26]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n0SHFJKb027201 for ; Wed, 28 Jan 2009 12:15:19 -0500 In-Reply-To: <1233100868.30154.103.camel@homeserver> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Tuesday 27 January 2009 07:01:08 pm LC Bruzenak wrote: > Even when I get a successful return value (from audit_log_user_message), > I don't get my string back out in "ausearch" unless it is WAY smaller - > ~1K or less I think. > > Any ideas/thoughts? I tested like this: auditctl -m `perl -e '{print "A"x"2048"}'` and found its getting cutoff just under 1K. So, I checked the kernel code and found this: 761 if (msg_type != AUDIT_USER_TTY) 762 audit_log_format(ab, " msg='%.1024s'", 763 (char *)data); 764 else { Offhand, I don't remember why the kernel sets the limit so low. It could be bumped some. How much, I don't know. 4K or 8K would seem fine. -Steve