From: Steve Grubb <sgrubb@redhat.com>
To: Kay Hayen <kayhayen@gmx.de>
Cc: linux-audit@redhat.com, alex@segv.de
Subject: Re: Audit for live supervision
Date: Tue, 19 Aug 2008 16:47:16 -0400 [thread overview]
Message-ID: <200808191647.16340.sgrubb@redhat.com> (raw)
In-Reply-To: <200808192233.59007.kayhayen@gmx.de>
On Tuesday 19 August 2008 16:33:58 Kay Hayen wrote:
> > Only one audit pid is allowed for security purposes.
>
> Damn security. I saw that patch while googling, and hoped it wasn't merged,
> but seems it was.
Its been there since 2.6.6 kernel. IOW - day 1.
> I don't really understand why it is helping security, if I need to kill
> auditd before I can open the netlink socket. For both I need root rights.
The queueing is complicated and if you have a group of processes it gets real
messy. The audit queue tries hard for guaranteed delivery or take the system
down if the flow is not working right. Its not like syslog or iptables
logging.
> There isn't any SELinux in the play, is there?
SE Linux helps for MLS systems, but for CAPP, it doesn't come into play. The
data flowing through the audit system could be very sensitive. Anyone needing
access to the stream either needs to replace auditd, write their own
dispatcher, or write a plugin to the shipped dispatcher. This way the admin
knows exactly what processes have access to the data.
-Steve
next prev parent reply other threads:[~2008-08-19 20:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 7:14 Audit for live supervision Kay Hayen
2008-08-14 14:04 ` Steve Grubb
2008-08-15 6:43 ` Kay Hayen
2008-08-15 12:54 ` Steve Grubb
2008-08-16 11:19 ` Kay Hayen
2008-08-18 15:10 ` Steve Grubb
2008-08-19 6:45 ` Kay Hayen
2008-08-19 14:14 ` John Dennis
2008-08-19 17:46 ` Kay Hayen
2008-08-19 18:18 ` Steve Grubb
2008-08-19 14:47 ` Steve Grubb
2008-08-19 18:23 ` Kay Hayen
2008-08-19 18:39 ` Steve Grubb
2008-08-19 20:33 ` Kay Hayen
2008-08-19 20:47 ` Steve Grubb [this message]
2008-08-19 21:35 ` Kay Hayen
2008-08-19 21:47 ` Steve Grubb
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=200808191647.16340.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=alex@segv.de \
--cc=kayhayen@gmx.de \
--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