public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: ramsdell@mitre.org (John D. Ramsdell)
To: linux-audit@redhat.com
Subject: Ptrace looses track of a forked child
Date: 30 Jun 2007 10:14:53 -0400	[thread overview]
Message-ID: <ogtsl89jzqa.fsf@oolong.mitre.org> (raw)

I thought I was very close to finishing up an application that uses
the audit system to perform a task formally done by a modified version
of strace.  Alas, one of the programs I had working last October no
longer works.

The broken program uses ptrace to add an audit rule for each child
process forked by the traced application.  It adds the rule before the
child runs by handling a SIGTRAP generated as a result of tracing the
original child with the PTRACE_O_TRACEFORK option.

I tried to follow to the changes to kernel/ptrace.c via linuxhq, but I
got little from that exercise.  I ended up submitting a bug report
here:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246330

If there is something else I should be doing, please advise.

I notice there are two other ptrace related bugs reported for Fedora
7.  Both have been assigned to Roland McGrath, a primary maintainer of
strace.  I bet he gets assigned this bug report too.  Roland doesn't
like the changes I make to strace that allows it to display the
security contexts associated with traced objects, so he'll remember
me.

One final question.  Has there been any other efforts aimed at
allowing the audit system to follow forks of traced processes?
Alternatives to my ptrace solution would be greatly appreciated at
this time.

John

             reply	other threads:[~2007-06-30 14:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-30 14:14 John D. Ramsdell [this message]
2007-07-23 18:51 ` Ptrace looses track of a forked child 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=ogtsl89jzqa.fsf@oolong.mitre.org \
    --to=ramsdell@mitre.org \
    --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