From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v1 0/6] Various fixes to the ntp policy module
Date: Tue, 14 Aug 2012 09:32:17 -0400 [thread overview]
Message-ID: <502A5361.1050100@tresys.com> (raw)
In-Reply-To: <1344855134-32212-1-git-send-email-dominick.grift@gmail.com>
On 08/13/12 06:52, Dominick Grift wrote:
> The previous patch was bad.
>
> Dominick Grift (6):
> Introduce ntp_conf_t config file type and use that instead of
> net_conf_t so that ntp_admin() does not need access to network
> configuration to be able to manage ntpd.
> There is no need for ntp_admin() to be able to get attributes of the
> ntpd process.
> Allow ntp_admin() to manage ntp_drift_t content.
> Allow ntp_admin() to list etc_t directories to be able to list ntp
> configuration content.
> Use "Role allowed access." for consistency
> Use permissions sets for compatibility.
>
> ntp.fc | 4 ++--
> ntp.if | 11 ++++++-----
> ntp.te | 7 ++++++-
> 3 files changed, 14 insertions(+), 8 deletions(-)
>
patches 1, 3-6 merged.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2012-08-14 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 10:52 [refpolicy] [PATCH v1 0/6] Various fixes to the ntp policy module Dominick Grift
2012-08-13 10:52 ` [refpolicy] [PATCH v1 1/6] Introduce ntp_conf_t Dominick Grift
2012-08-13 10:52 ` [refpolicy] [PATCH v1 2/6] Remove getattr permision from ntp_admin() Dominick Grift
2012-08-14 12:40 ` Christopher J. PeBenito
2012-08-14 13:15 ` Dominick Grift
2012-08-14 13:38 ` Christopher J. PeBenito
2012-08-13 10:52 ` [refpolicy] [PATCH v1 3/6] Allow ntp_admin() to manage ntp_drift_t content Dominick Grift
2012-08-13 10:52 ` [refpolicy] [PATCH v1 4/6] List etc_t directories Dominick Grift
2012-08-13 10:52 ` [refpolicy] [PATCH v1 5/6] Use "Role allowed access." for consistency Dominick Grift
2012-08-13 10:52 ` [refpolicy] [PATCH v1 6/6] Use permissions sets for compatibility Dominick Grift
2012-08-14 13:32 ` Christopher J. PeBenito [this message]
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=502A5361.1050100@tresys.com \
--to=cpebenito@tresys.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.