From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] system_logging.patch
Date: Tue, 24 Mar 2009 10:06:46 -0400 [thread overview]
Message-ID: <49C8E8F6.6050706@redhat.com> (raw)
http://people.fedoraproject.org/~dwalsh/SELinux/F11/system_logging.patch
New audit file context
log files under /var/spool
auditd calls getpw
audisp_t needs dac_override
audisp_t signals its self and its plugins
audisp_t will execute binaries and shell scripts
Sends dbus messages to all levels, audit runs at system_high so we need
to send dbus messages to daemons running at different levels.
audisp_t calls getpw
audisp uses dbus
audisp_remote binds to audit port to listen for incoming connections
uses getpw
next reply other threads:[~2009-03-24 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 14:06 Daniel J Walsh [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-26 23:39 [refpolicy] system_logging.patch Daniel J Walsh
2010-02-23 22:16 Daniel J Walsh
2010-03-17 18:40 ` Christopher J. PeBenito
2010-03-18 20:09 ` Daniel J Walsh
2009-11-12 22:13 Daniel J Walsh
2009-11-24 14:32 ` Christopher J. PeBenito
2009-11-24 15:56 ` Daniel J Walsh
2009-11-24 15:57 ` Daniel J Walsh
2008-09-24 19:33 Daniel J Walsh
2008-10-09 18:09 ` Christopher J. PeBenito
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=49C8E8F6.6050706@redhat.com \
--to=dwalsh@redhat.com \
--cc=refpolicy@oss.tresys.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.