From: LC Bruzenak <lenny@magitekltd.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: user message limits
Date: Mon, 08 Jun 2009 17:08:33 -0500 [thread overview]
Message-ID: <1244498913.15030.60.camel@homeserver> (raw)
In-Reply-To: <200901281215.16996.sgrubb@redhat.com>
On Wed, 2009-01-28 at 12:15 -0500, Steve Grubb wrote:
> 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
I apologize in advance, but I've lost the bubble on input event length.
Is there a plan for the kernel to allow bigger buffers in to be audited?
As of my current one (2.6.29.4-75.fc10) I'm still in the same ~900 byte
range.
To me, it seems that an increase would be automatically
backward-compatible. The "dropoff" point would just extend out a ways...
Thx,
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
prev parent reply other threads:[~2009-06-08 22:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 0:01 user message limits LC Bruzenak
2009-01-28 15:30 ` LC Bruzenak
2009-01-28 17:15 ` Steve Grubb
2009-01-28 17:44 ` LC Bruzenak
2009-01-28 20:14 ` Steve Grubb
2009-01-28 20:30 ` LC Bruzenak
2009-01-28 21:04 ` LC Bruzenak
2009-01-28 23:37 ` Casey Schaufler
2009-01-28 23:52 ` LC Bruzenak
2009-01-29 0:36 ` Casey Schaufler
2009-01-29 6:57 ` James W. Hoeft
2009-01-30 4:49 ` Casey Schaufler
2013-09-17 14:48 ` Richard Guy Briggs
2013-09-17 18:10 ` Steve Grubb
2013-09-18 2:25 ` Richard Guy Briggs
2013-09-18 14:25 ` Steve Grubb
2013-09-18 15:10 ` spurious \n in session id helper [was: Re: user message limits] Richard Guy Briggs
2009-06-08 22:08 ` LC Bruzenak [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=1244498913.15030.60.camel@homeserver \
--to=lenny@magitekltd.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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