public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Amy Griffis <amy.griffis@hp.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: [PATCH] audit=0 appears not to completely disable auditing
Date: Mon, 02 Apr 2007 15:17:01 -0400	[thread overview]
Message-ID: <16942.1175541421@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 02 Apr 2007 14:57:11 EDT." <20070402185711.GA21145@fc.hp.com>


[-- Attachment #1.1: Type: text/plain, Size: 870 bytes --]

On Mon, 02 Apr 2007 14:57:11 EDT, Amy Griffis said:
> Steve Grubb wrote:  [Thu Mar 22 2007, 05:55:45PM EDT]
> > > If you want audit_enabled=0 to turn off audit completely, do you also
> > > want to drop selinux messages?
> > 
> > No, the SE Linux folks want avc messages at all times unless the admin 
> > specifically sets a rule to suppress them. 
> 
> Okay, makes sense. Do you think audit should return an error if
> someone tries to add a rule when audit_enabled=0 ?

Yes, probably.  You'd kind of think that the human doing the auditing would
like a large and loud complaint if auditing had been accidentally disabled.

The only question is what behavior it should have if a site (for whatever
reason) decides to first load all the rules, then enable auditing (possibly
to avoid spurious complaints about processes because not all the rules have
been loaded yet).

[-- Attachment #1.2: Type: application/pgp-signature, Size: 226 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2007-04-02 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09 20:50 [PATCH] audit=0 appears not to completely disable auditing Steve Grubb
2007-03-22 21:45 ` Amy Griffis
2007-03-22 21:55   ` Steve Grubb
2007-04-02 18:57     ` Amy Griffis
2007-04-02 19:17       ` Valdis.Kletnieks [this message]
2007-09-26 16:52 ` Eric Paris

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=16942.1175541421@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=amy.griffis@hp.com \
    --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