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: 15 Oct 2006 11:32:07 -0400 [thread overview]
Message-ID: <ogt4pu5lhmw.fsf@divan.mitre.org> (raw)
In-Reply-To: <200610131007.53543.sgrubb@redhat.com>
Steve Grubb <sgrubb@redhat.com> writes:
> It was using auditctl just for expedience when the program was
> written. I can add the code to switch it over.
I wrote code that uses libaudit to add rules. After performing "yum
install audit-libs-devel", I was pleased to find a manual page for
audit_add_rule, but the description of the return value says to refer
to audit_send. However, I found no manual page for audit_send.
Studying code made me realize the error condition is <= 0, not < 0, so
it's important not to guess.
John
static int audit_sys; /* File descriptor for socket to audit system */
static int /* Create a rule for a pid */
init_rule(struct audit_rule *r, pid_t pid)
{ /* Returns zero on success */
char field[PID_FIELD_SIZE];
if (snprintf(field, PID_FIELD_SIZE, "pid=%d", pid) >= PID_FIELD_SIZE) {
fprintf(stderr, "Internal error in init_rule\n");
exit(1);
}
memset(r, 0, sizeof(*r));
if (audit_rule_syscallbyname(r, "all") < 0) {
fprintf(stderr, "Illegal syscall name for audit rule for %d\n", pid);
return 1;
}
if (audit_rule_fieldpair(r, field, AUDIT_FILTER_ENTRY)) {
fprintf(stderr, "Cannot add field to audit rule for %d\n", pid);
return 1;
}
return 0;
}
/* Equivalent to '/sbin/auditctl -a entry,always -F pid=%d -S all' */
static int
add_rule(pid_t pid) /* Returns zero on success */
{
int i;
for (i = 0; i < nchildren; i++)
if (pid == children[i]) /* Rule already present */
return 0;
if (nchildren >= MAX_CHILDREN) {
fprintf(stderr, "Too many children\n");
return 1;
}
struct audit_rule r[1];
if (init_rule(r, pid))
return 1;
if (audit_add_rule(audit_sys, r, AUDIT_FILTER_ENTRY, AUDIT_ALWAYS) <= 0) {
fprintf(stderr, "Cannot add an audit rule for %d\n", pid);
return 1;
}
children[nchildren++] = pid;
return 0;
}
next prev parent reply other threads:[~2006-10-15 15:32 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
2006-10-13 14:07 ` Steve Grubb
2006-10-15 15:32 ` John D. Ramsdell [this message]
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=ogt4pu5lhmw.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.