All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com, aaw@google.com
Subject: Re: [patch 058/209] audit: rework execve audit
Date: Sat, 28 Jul 2007 00:06:21 +0200	[thread overview]
Message-ID: <1185573981.15205.57.camel@lappy> (raw)
In-Reply-To: <1185573344.15205.54.camel@lappy>

On Fri, 2007-07-27 at 23:55 +0200, Peter Zijlstra wrote:
> On Fri, 2007-07-27 at 16:57 -0400, Steve Grubb wrote:
> 
> > I don't know of anything special its a fully updated rawhide machine. I am not 
> > running any tests, this is at the prompt in runlevel 3. I have audit=1 as a 
> > boot parameter in grub.conf and very simple audit rules for that machine:
> > 
> > -D
> > -b 256
> > -a exit,always -S sethostname
> > -w /etc/selinux/config
> > 
> > which is not exotic.
> 
> I'm feeling dumb,.. on fedora 7 userland I do:
> 
> [root@opteron ~]# auditctl -D
> No rules
> [root@opteron ~]# auditctl -b 256
> AUDIT_STATUS: enabled=0 flag=1 pid=0 rate_limit=0 backlog_limit=256 lost=0 backlog=0
> [root@opteron ~]# auditctl -a exit,always -S sethostname
> Error sending add rule request (Invalid argument)
> 
> man auditctl seems to suggest that is a valid command.

Ok, I am dumb, CONFIG_AUDITSYSCALL=n

  reply	other threads:[~2007-07-27 22:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19  8:48 [patch 058/209] audit: rework execve audit akpm
2007-07-27 20:13 ` Steve Grubb
2007-07-27 20:44   ` Peter Zijlstra
2007-07-27 20:57     ` Steve Grubb
2007-07-27 21:55       ` Peter Zijlstra
2007-07-27 22:06         ` Peter Zijlstra [this message]
2007-07-27 22:24           ` Peter Zijlstra
2007-07-27 20:50   ` Alexander Viro
2007-07-27 21:03   ` Alexander Viro
2007-07-27 21:11     ` Steve Grubb
2007-07-27 21:21       ` Alexander Viro
2007-07-27 22:55   ` [PATCH] audit: fix two bugs in the new execve audit code Peter Zijlstra
2007-07-27 23:05     ` Andrew Morton
2007-07-28  2:05     ` 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=1185573981.15205.57.camel@lappy \
    --to=a.p.zijlstra@chello.nl \
    --cc=aaw@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.