From: ramsdell@mitre.org (John D. Ramsdell)
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: An autrace that follows forks
Date: 12 Oct 2006 06:51:38 -0400 [thread overview]
Message-ID: <ogt8xjlbydh.fsf@divan.mitre.org> (raw)
In-Reply-To: <200610111624.54540.sgrubb@redhat.com>
Steve Grubb <sgrubb@redhat.com> writes:
> 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.
Do you mean this is a problem that requires a kernel side
implementation to do it well? Ptracing the descendants has the down
side of changing the behavior of an application due to all the tracing
signals, but until a kernel side implementation is available, the
ptracing solution seems to me to be the only way to get the audit data
we desire. Or do you mean the idea of using ptrace to follow forks is
flawed for some reason, and will not work?
One quick question, I notice autrace.c invokes /sbin/auditctl to
change audit rules, but shouldn't it being using audit_add_rule and
friends instead? I'll implement this change if you want me to.
John
next prev parent reply other threads:[~2006-10-12 10:51 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
2006-10-12 10:51 ` John D. Ramsdell [this message]
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=ogt8xjlbydh.fsf@divan.mitre.org \
--to=ramsdell@mitre.org \
--cc=linux-audit@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