From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 18/34]: patch for the policykit module (labeling, start from dbus, read xdm files)
Date: Wed, 2 Mar 2011 15:47:03 +0100 [thread overview]
Message-ID: <20110302144702.GA20297@siphos.be> (raw)
In-Reply-To: <4D6E4B6A.5090708@tresys.com>
On Wed, Mar 02, 2011 at 08:51:38AM -0500, Christopher J. PeBenito wrote:
[... About when dontaudit is advantageous ...]
> In general, anything that is not required should be denied. We do not
> want to fill up the logs with extraneous denial messages, so we
> dontaudit them. If there is a question of denials being suppressed by
> dontaudits, thats why we have semodule -D.
Yup.
What we do within Gentoo Hardened during the policy development is to
embrace the dontaudits that we *think* can be used within a tunable
(gentoo_try_dontaudit). It allows us and testers to validate if the policy
is good (and doesn't fill the audit logs with unnecessary denials) but still
leave some granularity (the boolean) before really disabling all dontaudit
statements.
Eventually, when we're more confident that the dontaudit is really
opportunistic, then we'll remove it from the tunable and also suggest it for
inclusion in the reference policy.
Wkr,
Sven Vermeulen
next prev parent reply other threads:[~2011-03-02 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 6:22 [refpolicy] [PATCH 18/34]: patch for the policykit module (labeling, start from dbus, read xdm files) Guido Trentalancia
2011-02-28 13:56 ` Christopher J. PeBenito
2011-02-28 15:28 ` Daniel J Walsh
2011-02-28 19:07 ` Guido Trentalancia
2011-03-01 19:12 ` Christopher J. PeBenito
2011-03-01 22:47 ` Guido Trentalancia
2011-03-02 13:51 ` Christopher J. PeBenito
2011-03-02 14:47 ` Sven Vermeulen [this message]
2011-03-02 19:55 ` Guido Trentalancia
2011-03-03 13:28 ` 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=20110302144702.GA20297@siphos.be \
--to=sven.vermeulen@siphos.be \
--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.