From: Klaus Weidner <klaus@atsec.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Linux-audit@redhat.com
Subject: Re: Auditing File Changes
Date: Mon, 10 Jul 2006 16:15:18 -0500 [thread overview]
Message-ID: <20060710211517.GC6780@w-m-p.com> (raw)
In-Reply-To: <20060710202405.18458.qmail@web36606.mail.mud.yahoo.com>
On Mon, Jul 10, 2006 at 01:24:05PM -0700, Casey Schaufler wrote:
> --- Klaus Weidner <klaus@atsec.com> wrote:
> > How about using FUSE (userspace file system) on top of a version
> > control system (git, subversion, ...), and using the version control
> > system's change records to keep track of the full history?
>
> I donno, those small writes are going to be kind of slow.
Hmm, I wonder how much would break if the filesystem treated the close()
as a commit in the version control system, with the changes not being
visible to other processes until that happens...
(or exit() instead of close() for a more transactional approach)
-Klaus
prev parent reply other threads:[~2006-07-10 21:15 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
2006-07-10 19:46 ` Klaus Weidner
2006-07-10 20:24 ` Casey Schaufler
2006-07-10 21:15 ` Klaus Weidner [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=20060710211517.GC6780@w-m-p.com \
--to=klaus@atsec.com \
--cc=Linux-audit@redhat.com \
--cc=casey@schaufler-ca.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