mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <mulix@mulix.org>
To: Rik Faith <faith@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	okir@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] Light-weight Auditing Framework
Date: Wed, 3 Mar 2004 10:55:01 +0200	[thread overview]
Message-ID: <20040303085501.GC31052@mulix.org> (raw)
In-Reply-To: <16451.40189.997259.379123@neuro.alephnull.com>

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

On Mon, Mar 01, 2004 at 03:28:45PM -0500, Rik Faith wrote:

> > Whether we want syscall auditing in mainline is a completely different
> > question..
> 
> I believe we need a light-weight, maintainable framework that is
> versatile enough to be used for non-security purposes (e.g., debugging).
> In general, my patch meets these requirements since it provides very
> little that helps specifically with security (failure modes, loginuid,
> and small helper functions).

I'd like to second the sentiment - for syscalltrack, we would love to
have a framework that can be used for debugging system call events. 

Cheers, 
Muli 
-- 
Muli Ben-Yehuda
http://www.mulix.org | http://mulix.livejournal.com/


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

  parent reply	other threads:[~2004-03-03  9:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01 16:28 Rik Faith
2004-03-01 19:45 ` Christoph Hellwig
2004-03-01 20:28   ` Rik Faith
2004-03-02  9:44     ` Olaf Kirch
2004-03-02 11:09       ` Rik Faith
2004-03-02 15:02         ` Rik Faith
2004-03-03  8:55     ` Muli Ben-Yehuda [this message]
2004-03-03 11:21       ` Rik Faith
2004-03-01 20:26 ` Chris Wright
2004-03-02 21:49   ` Rik Faith
2004-03-03  0:49     ` Chris Wright
2004-03-03 10:57       ` Rik Faith

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=20040303085501.GC31052@mulix.org \
    --to=mulix@mulix.org \
    --cc=faith@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=okir@suse.de \
    /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

all inboxes | Powered by JetHome®