From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: An autrace that follows forks
Date: Wed, 11 Oct 2006 16:24:54 -0400 [thread overview]
Message-ID: <200610111624.54540.sgrubb@redhat.com> (raw)
In-Reply-To: <ogtbqoiwraf.fsf@divan.mitre.org>
On Wednesday 11 October 2006 16:06, John D. Ramsdell wrote:
> I plan to write a version of autrace that follows forks.
This is a problem that requires a kernel side implementation. We've talked
about it in the past and I don't think we've got code yet. We did add audit
by ppid which helps a little. But we need a generic way to say that we want
to audit a specific program and all its descendants.
-Steve
next prev parent reply other threads:[~2006-10-11 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 20:06 An autrace that follows forks John D. Ramsdell
2006-10-11 20:24 ` Steve Grubb [this message]
2006-10-12 10:51 ` John D. Ramsdell
2006-10-13 14:07 ` Steve Grubb
2006-10-15 15:32 ` John D. Ramsdell
2006-10-11 20:55 ` James Antill
2006-10-12 11:09 ` John D. Ramsdell
2006-10-12 11:40 ` John D. Ramsdell
2006-10-13 13:50 ` John D. Ramsdell
2006-10-15 15:38 ` John D. Ramsdell
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=200610111624.54540.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox