From: dsugar@tresys.com (Dave Sugar)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 0/5-v4] Updates for chronyd
Date: Mon, 5 Mar 2018 09:02:57 -0500 [thread overview]
Message-ID: <20180305140302.31341-1-dsugar@tresys.com> (raw)
This patch set is several changes to the chronyd module to achieve the following things:
1) Separate type for /etc/chrony.conf along with interfaces.
v2 - fix a comment in the patch
2) Interfaces to start/stop/status/etc.. the chronyd service
v2 - fix a comment in the patch
3) Allow chronyd to send/recv ntp client packets
4) New type for chronyc - it is run from chrony-wait.service but it was running in init_t domain
v2 - incorporate feedback on interface names & fix denial related to chowning /var/run/chrony
5) Add interface to domtrans into chronyc domain
v2 - incorporate feedback on interface names & allow cli access to tty
v4 - Try one last time to submit via email. If this still fails I will try a pull request on GitHub.
chronyd.fc | 2 +
chronyd.if | 161 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
chronyd.te | 60 ++++++++++++++++++++++-
3 files changed, 221 insertions(+), 2 deletions(-)
--
2.14.3
next reply other threads:[~2018-03-05 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 14:02 Dave Sugar [this message]
2018-03-05 14:02 ` [refpolicy] [PATCH 1/5-v4] Separate type for chronyd config file Dave Sugar
2018-03-05 14:02 ` [refpolicy] [PATCH 2/5-v4] Add interface to start/stop/enable/disable/status of chronyd service Dave Sugar
2018-03-05 14:03 ` [refpolicy] [PATCH 3/5-v4] Chronyd talks ntp client packets to get time from server Dave Sugar
2018-03-05 14:03 ` [refpolicy] [PATCH 4/5-v4] Policy for chronyc - it was running in init_t domain Dave Sugar
2018-03-05 14:03 ` [refpolicy] [PATCH 5/5-v4] Allow execution of chronyc from commandline Dave Sugar
2018-03-07 21:57 ` [refpolicy] [PATCH 0/5-v4] Updates for chronyd Chris 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=20180305140302.31341-1-dsugar@tresys.com \
--to=dsugar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).