From: Steve Grubb <sgrubb@redhat.com>
To: Matthew Booth <mbooth@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Which userspace packages modified for audit
Date: Sun, 25 Feb 2007 18:07:34 -0500 [thread overview]
Message-ID: <200702251807.34900.sgrubb@redhat.com> (raw)
In-Reply-To: <1172442908.1541.6.camel@localhost.localdomain>
On Sunday 25 February 2007 17:35:08 Matthew Booth wrote:
>> There are several APIs to enforce consistent messages depending on the
>> purpose. They all start with audit_log_ .
>
> That's a lot of choices. I specifically want to log a message in my
> ausetauid utility containing the fully command line executed under a
> different auid.
You would need to build your message in a buffer and pass it to
audit_log_user_message() as the message param since an API has not been built
for the purpose you described in 1.0.15. You will also want to follow naming
conventions laid out in the parsing spec.
> To make sure it turns up in searches, I want it to have the same audit event
> ID as the LOGIN message it generates.
No can do.
> Is this achievable, and which function should I read the source for ;) ?
Nope. Setting the loginuid is a discrete event seen from the kernel's
perspective.
-Steve
prev parent reply other threads:[~2007-02-25 23:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 23:03 Which userspace packages modified for audit Tony Jones
2007-02-23 10:18 ` SUSE ELS and Audit Johnston Mark (UK)
2007-02-23 10:20 ` Marcus Meissner
2007-02-23 10:26 ` Roman Drahtmueller
2007-02-23 10:59 ` Johnston Mark (UK)
2007-02-23 11:47 ` Which userspace packages modified for audit Steve Grubb
2007-02-23 14:22 ` Matthew Booth
2007-02-25 18:41 ` Steve Grubb
2007-02-25 18:41 ` Marcus Meissner
2007-02-25 19:40 ` Steve Grubb
2007-02-26 13:21 ` Marcus Meissner
2007-02-26 14:40 ` Steve Grubb
2007-02-25 22:15 ` Matthew Booth
2007-02-25 22:30 ` Steve Grubb
2007-02-25 22:35 ` Matthew Booth
2007-02-25 23:07 ` Steve Grubb [this message]
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=200702251807.34900.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=mbooth@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