From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: EXT :Re: CD Burner Auditing
Date: Tue, 22 Apr 2014 16:43:58 -0400 [thread overview]
Message-ID: <1904802.QI4G1AM2hm@x2> (raw)
In-Reply-To: <1884427.kS0bph9V2f@x2>
On Tuesday, April 22, 2014 04:02:47 PM Steve Grubb wrote:
> > You can use audit dispatcher to react to audit events.... When u get a
> > MOUNT event you can see where sr0 is mounted and start a new watch for
> > that
> > path. If you are not writing an ISO I think it has to be mounted.
>
> I think hooking the udev rules might be better. This would let you check
> for hot plug events where something is not yet mounted.
A long time ago during the RHEL5 LSPP certification, there was a project
created to help audit device allocation:
http://sourceforge.net/projects/devallocator/
There were 2 audit events created to assist in this. But if I recall, there
was a decision made to not support hot plug events. I forget why. The main
thing is that the code has the event in it formatted correctly. udev could be
patched to provide this event.
-Steve
next prev parent reply other threads:[~2014-04-22 20:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 19:14 CD Burner Auditing Boyce, Kevin P. (AS)
2014-04-22 19:32 ` Satish Chandra Kilaru
2014-04-22 19:35 ` EXT :Re: " Boyce, Kevin P. (AS)
2014-04-22 19:39 ` Satish Chandra Kilaru
2014-04-22 19:44 ` Boyce, Kevin P. (AS)
2014-04-22 19:55 ` Satish Chandra Kilaru
2014-04-22 20:06 ` Steve Grubb
2014-04-22 20:39 ` Steve Grubb
2014-04-22 22:00 ` Burn Alting
2014-04-22 22:11 ` Steve Grubb
2014-04-23 0:13 ` Josh
2014-04-22 20:02 ` Steve Grubb
2014-04-22 20:43 ` Steve Grubb [this message]
2014-04-22 21:52 ` Burn Alting
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=1904802.QI4G1AM2hm@x2 \
--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 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.