From: Matthew Booth <mbooth@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux Audit <linux-audit@redhat.com>
Subject: Re: AUDIT_SIGNAL_INFO
Date: Mon, 23 Mar 2009 18:01:50 +0000 [thread overview]
Message-ID: <49C7CE8E.2000602@redhat.com> (raw)
In-Reply-To: <1237831179.5667.7.camel@localhost.localdomain>
Eric Paris wrote:
> On Mon, 2009-03-23 at 15:29 +0000, Matthew Booth wrote:
>> Under what circumstances will the RHEL 4 kernel generate a message of
>> type AUDIT_SIGNAL_INFO? My understanding is that it should be sent when
>> a process sends a signal to the audit daemon, however I have not
>> observed that. Any ideas?
>
> AUDIT_SIGNAL_INFO is sent when the kernel gets an AUDIT_SIGNAL_INFO
> request from auditd.
>
> Basically if you send a signal to the audit daemon, the audit daemon
> sends a message to the kernel requesting AUDIT_SIGNAL_INFO. The kernel
> sends the info back to auditd. Auditd then uses that info to log about
> the signal it took. auditd then acts on the signal it took.
>
> So you wouldn't see it in the normal audit logs. it's really just a
> communication medium between the kernel and auditd.
That makes sense. Looking in libaudit.h, I assume you end up with one of
these:
/* data structure for who signaled the audit daemon */
struct audit_sig_info {
uid_t uid;
pid_t pid;
char ctx[0];
};
Does this give any information in addition to what you'd get from
siginfo_t, or is it inherently more reliable?
Also, is there any way to notice you were sent a KILL or a STOP?
Thanks,
Matt
--
Matthew Booth, RHCA, RHCSS
Red Hat, Global Professional Services
M: +44 (0)7977 267231
GPG ID: D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
next prev parent reply other threads:[~2009-03-23 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 15:29 AUDIT_SIGNAL_INFO Matthew Booth
2009-03-23 15:43 ` AUDIT_SIGNAL_INFO Steve Grubb
2009-03-23 17:59 ` AUDIT_SIGNAL_INFO Eric Paris
2009-03-23 18:01 ` Matthew Booth [this message]
2009-03-23 19:32 ` AUDIT_SIGNAL_INFO Eric Paris
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=49C7CE8E.2000602@redhat.com \
--to=mbooth@redhat.com \
--cc=eparis@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 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.