From: Linda Knippers <linda.knippers@hp.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: redhat-lspp@redhat.com, linux-audit@redhat.com
Subject: Re: Watch Performance
Date: Tue, 11 Apr 2006 17:21:01 -0400 [thread overview]
Message-ID: <443C1DBD.5040103@hp.com> (raw)
In-Reply-To: <200604111701.23649.sgrubb@redhat.com>
Steve Grubb wrote:
> I also don't like the idea of handling this by all those syscalls or using
> "all" because user space tools could get out of sync with the kernel. On any
> kernel upgrade, there could be a new syscall that allows file system access.
> The user space tools wouldn't know about it and wouldn't provide automatic
> coverage.
Maybe we ought to have a way to specific all system calls of a
particular type and let the kernel audit code decides which ones
those are. We could group file operations, mode changes, ownership
changes, privilege changes, execs, time changes, etc. That way
admins don't necessarily have to know all the different ways one
might do a chown, lchown, fchown, etc. And maybe there should be
an 'all' that really means 'all' and not just all that the user
space tools know about.
-- ljk
next prev parent reply other threads:[~2006-04-11 21:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 16:21 Watch Performance Steve Grubb
2006-04-09 19:48 ` Steve Grubb
2006-04-11 13:12 ` Steve Grubb
2006-04-11 3:51 ` Amy Griffis
2006-04-11 10:26 ` Steve Grubb
2006-04-11 16:11 ` Amy Griffis
2006-04-11 21:01 ` Steve Grubb
2006-04-11 21:21 ` Linda Knippers [this message]
2006-04-12 21:15 ` Amy Griffis
2006-04-17 15:27 ` Timothy R. Chavez
2006-04-17 20:06 ` Klaus Weidner
2006-04-21 15:01 ` Amy Griffis
2006-04-21 15:13 ` Steve Grubb
2006-04-21 15:10 ` Linda Knippers
2006-04-21 16:07 ` Alexander Viro
2006-04-24 15:34 ` Amy Griffis
2006-05-10 15:32 ` Steve Grubb
2006-05-10 16:34 ` Alexander Viro
2006-05-10 19:23 ` Steve Grubb
2006-05-10 19:37 ` Alexander Viro
2006-05-10 19:51 ` 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=443C1DBD.5040103@hp.com \
--to=linda.knippers@hp.com \
--cc=linux-audit@redhat.com \
--cc=redhat-lspp@redhat.com \
--cc=sgrubb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox