All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Beattie <sbeattie@suse.de>
To: Linux Audit <linux-audit@redhat.com>
Subject: Re: [PATCH] audit config lockdown
Date: Sat, 27 Jan 2007 00:13:07 -0800	[thread overview]
Message-ID: <20070127081307.GA360@suse.de> (raw)
In-Reply-To: <200701191439.55315.sgrubb@redhat.com>


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

On Fri, Jan 19, 2007 at 02:39:55PM -0500, Steve Grubb wrote:
> The following patch adds a new mode to the audit system. It uses the
> audit_enabled config option to introduce the idea of audit enabled, but
> configuration is immutable. Any attempt to change the configuration 
> while in this mode is audited. To change the audit rules, you'd need to
> reboot the machine.

Seems reasonable to me. Just a couple of comments.

> This patch also adds "res=" to a number of configuration commands that did not
> have it before.

The res= idiom is unfamiliar to me, seems like an is_xxx name
(is_allowed?) would make it clear what the intent is for.

> @@ -64,7 +64,9 @@
>   * (Initialization happens after skb_init is called.) */
>  static int	audit_initialized;
>  
> -/* No syscall auditing will take place unless audit_enabled != 0. */
> +/* 0 - no auditing
> + * 1 - auditing enabled
> + * 2 - auditing enabled and configuration is locked/unchangeable. */
>  int		audit_enabled;

You probably want a #define or enum for these values, rather than
using magic numbers.

Thanks.
-- 
Steve Beattie
SUSE Labs, Novell Inc. 
<sbeattie@suse.de>
http://NxNW.org/~steve/

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

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



  parent reply	other threads:[~2007-01-27  8:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 19:39 [PATCH] audit config lockdown Steve Grubb
2007-01-19 19:48 ` Casey Schaufler
2007-01-27  8:13 ` Steve Beattie [this message]
2007-01-27 13: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=20070127081307.GA360@suse.de \
    --to=sbeattie@suse.de \
    --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 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.