From: David Sugar <dsugar@tresys.com>
To: "selinux-refpolicy@vger.kernel.org" <selinux-refpolicy@vger.kernel.org>
Subject: [PATCH 0/3] Grant permissions to read fips_enabled
Date: Sat, 8 Dec 2018 18:45:06 +0000 [thread overview]
Message-ID: <20181208184347.32575-1-dsugar@tresys.com> (raw)
Resoving a few issues with processed trying to read
/proc/sys/crypto/fips_enaled and being denied by SELinux policy.
Dave Sugar (3):
Allow X (xserver_t) to read /proc/sys/crypto/fips_enabled
Allow kmod to read /proc/sys/crypto/fips_enabled
Allow dbus to access /proc/sys/crypto/fips_enabled
policy/modules/services/dbus.te | 2 ++
policy/modules/services/xserver.te | 1 +
policy/modules/system/modutils.te | 1 +
3 files changed, 4 insertions(+)
--
2.19.2
next reply other threads:[~2018-12-08 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 18:45 David Sugar [this message]
2018-12-08 18:45 ` [PATCH 1/3] Allow X (xserver_t) to read /proc/sys/crypto/fips_enabled David Sugar
2018-12-11 22:54 ` Chris PeBenito
2018-12-08 18:45 ` [PATCH 2/3] Allow kmod " David Sugar
2018-12-11 22:54 ` Chris PeBenito
2018-12-08 18:45 ` [PATCH 3/3] Allow dbus to access /proc/sys/crypto/fips_enabled David Sugar
2018-12-11 22:54 ` 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=20181208184347.32575-1-dsugar@tresys.com \
--to=dsugar@tresys.com \
--cc=selinux-refpolicy@vger.kernel.org \
/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).