mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rik Faith <faith@redhat.com>
To: Muli Ben-Yehuda <mulix@mulix.org>
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 06:21:20 -0500	[thread overview]
Message-ID: <16453.49072.809252.290117@neuro.alephnull.com> (raw)
In-Reply-To: [Muli Ben-Yehuda <mulix@mulix.org>] Wed  3 Mar 2004 10:55:01 +0200

On Wed  3 Mar 2004 10:55:01 +0200, Muli Ben-Yehuda <mulix@mulix.org> wrote:
> 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. 

I should clarify to avoid any confusion.  The audit framework I am
proposing does _not_ allow for generic hooking of system calls.

However, the ability to audit the call is generic in the sense that
another part of the kernel can request that an audit record be generated
for the current in-progress system call (or filtering can be used to
request that audit records be generated).  Although this should be
sufficient for SELinux and other security infrastructures, as well as
many non-security uses, it would only support a subset of what
syscalltrack can do currently (i.e., audit can provide information about
the syscall, but can't be used to change the behavior of the syscall).


  reply	other threads:[~2004-03-03 11:21 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
2004-03-03 11:21       ` Rik Faith [this message]
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=16453.49072.809252.290117@neuro.alephnull.com \
    --to=faith@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mulix@mulix.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®