From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Current capabilities
Date: Wed, 13 Dec 2006 18:41:16 -0500 [thread overview]
Message-ID: <200612131841.16385.sgrubb@redhat.com> (raw)
In-Reply-To: <1166051787.6399.23.camel@cisco.sandia.gov>
On Wednesday 13 December 2006 18:16, Michael W Folsom wrote:
> 1) If someone tries to access an object (file, directory, program) that
> they don't have rights to the event needs to be recorded
-a always,exit -S open,opendir,execve -F exit=-13
This does it for 3 common syscalls. You can do it for any syscall you want.
You can use strace to figure out the syscalls you want.
> 2) if someone logs into a system and su's to another user or series of
> users their actions need to be traceable to the original login user's
> id
It does this. There is a process attribute, loginuid, that keeps track of
this. The audit events have it as the auid field. We've already preconfigured
RHEL4/5 and FC4->rawhide to handle this.
-Steve
prev parent reply other threads:[~2006-12-13 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 23:16 Current capabilities Michael W Folsom
2006-12-13 23:39 ` Linda Knippers
2006-12-14 12:43 ` Boyce, Kevin P. (Melbourne, FL)
2006-12-14 13:33 ` Steve Grubb
2006-12-13 23:41 ` 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=200612131841.16385.sgrubb@redhat.com \
--to=sgrubb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox