From: Chris Wright <chrisw@osdl.org>
To: Russell Miller <rmiller@duskglow.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: auditing subsystem
Date: Thu, 3 Mar 2005 22:34:21 -0800 [thread overview]
Message-ID: <20050304063421.GS28536@shell0.pdx.osdl.net> (raw)
In-Reply-To: <200503032218.12062.rmiller@duskglow.com>
* Russell Miller (rmiller@duskglow.com) wrote:
> I've been doing a lot of research on this, and I keep coming up with things
> that don't work, have been abandoned, or are almost impossible to find or get
> working. So I'll ask here. Maybe one of the ultra-elightened linux gods
> will have a ready answer.
You'll have better luck using linux-audit list.
> I want to be able to audit system calls - I want to log when files are opened,
> created, changed, deleted, etc. Preferably I would like to do it without
> having to apply kernel patches, using vanilla (or close to vanilla) kernel.
> If this isn't possible, my net preference is to use a module. If this isn't
> possible, well, I'll do what I have to.
No patches needed (although you will want 2.6.11 because the inode filter
was busted, and you'll likely want to use it), for opened anyway. You'll
need an additional auditfs patch for created/deleted/changed(for more
than just knowing open w/ write access) and it's not a stable patch yet.
> I notice there is a CONFIG_AUDIT option. Is this what I am looking for, and
> how do I use it? /dev/audit seems not to work...
You'll need auditd, auditctl, and some rules to capture what you care
about.
For example:
To watch accesses to /etc/passwd (not creation/deletion events).
# auditd
# auditctl -a entry,possible -S open
# auditctl -a exit,always -S open -F inode=(inode of /etc/passwd)
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-03-04 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 6:18 auditing subsystem Russell Miller
2005-03-04 6:34 ` Chris Wright [this message]
2005-03-04 6:53 ` Valdis.Kletnieks
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=20050304063421.GS28536@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmiller@duskglow.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.