From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Fwd: Re: system_logging.patch
Date: Thu, 18 Mar 2010 13:12:36 -0400 [thread overview]
Message-ID: <4BA25F04.7030105@redhat.com> (raw)
Can you comment on the levels of the sockets
-------- Original Message --------
Subject: Re: system_logging.patch
Date: Wed, 17 Mar 2010 14:40:11 -0400
From: Christopher J. PeBenito <cpebenito@tresys.com>
Organization: Tresys Technology, LLC
To: Daniel J Walsh <dwalsh@redhat.com>
CC: refpolicy at oss1.tresys.com
On Tue, 2010-02-23 at 17:16 -0500, Daniel J Walsh wrote:
> http://people.fedoraproject.org/~dwalsh/SELinux/F13/system_logging.patch
>
> New log context
>
> Allow setting audit tty
>
> Fixing interfaces
Why are the sockets being set to system high? Same thing for the pid
file? They don't have sensitive data.
The logging_manage_all_logs() change is excessive, as "manage" doesn't
include relabeling.
Why does auditd need to use nsswitch?
Otherwise merged.
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.tresys.com/pipermail/refpolicy/attachments/20100318/9014d0dc/attachment.html
next reply other threads:[~2010-03-18 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 17:12 Daniel J Walsh [this message]
[not found] ` <201003181615.22542.sgrubb@redhat.com>
2010-03-19 12:14 ` [refpolicy] Fwd: Re: system_logging.patch Christopher J. PeBenito
2010-03-19 12:22 ` Daniel J Walsh
2010-03-19 14:13 ` Christopher J. PeBenito
2010-03-19 14:18 ` Daniel J Walsh
[not found] ` <201003190944.18262.sgrubb@redhat.com>
2010-03-19 14:44 ` Christopher J. PeBenito
[not found] ` <201003191102.56364.sgrubb@redhat.com>
2010-03-19 15:21 ` Daniel J Walsh
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=4BA25F04.7030105@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.