All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Auditing File Changes
Date: Tue, 11 Jul 2006 09:20:48 -0400	[thread overview]
Message-ID: <200607110920.48392.sgrubb@redhat.com> (raw)
In-Reply-To: <3076.216.231.24.46.1152569340.squirrel@webmail.uci.edu>

On Monday 10 July 2006 18:09, eklinger@uci.edu wrote:
> The original idea was to prevent the user from opening the file in any
> text or hex editor and changing the file or the file's allowed operations,
> which would be stored in the file itself.

The access has already occured by the time the audit system tells you about 
it. You are simply too late. What you need its access control. The MCS 
capabilities in SE Linux/FC5 may help you. You can google for MCS.

-Steve

  parent reply	other threads:[~2006-07-11 13:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 17:29 Auditing File Changes eklinger
2006-07-10 17:42 ` Valdis.Kletnieks
2006-07-10 17:44 ` Steve Grubb
2006-07-10 19:32 ` Casey Schaufler
2006-07-10 19:42   ` Valdis.Kletnieks
2006-07-10 19:56     ` LC Bruzenak
2006-07-10 20:38       ` Valdis.Kletnieks
2006-07-10 20:51       ` Valdis.Kletnieks
2006-07-10 21:01         ` Klaus Weidner
2006-07-10 21:39           ` Casey Schaufler
2006-07-10 21:02         ` Timothy R. Chavez
2006-07-10 20:55       ` Timothy R. Chavez
2006-07-10 21:08         ` Timothy R. Chavez
2006-07-10 21:11       ` eklinger
2006-07-10 21:22         ` Valdis.Kletnieks
2006-07-10 21:37         ` Timothy R. Chavez
2006-07-10 22:09           ` eklinger
2006-07-10 23:37             ` Darren Cole
2006-07-11 12:56             ` Stephen John Smoogen
2006-07-11 13:20             ` Steve Grubb [this message]
2006-07-10 19:46   ` Klaus Weidner
2006-07-10 20:24     ` Casey Schaufler
2006-07-10 21:15       ` Klaus Weidner

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=200607110920.48392.sgrubb@redhat.com \
    --to=sgrubb@redhat.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 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.