From: Topi Miettinen <toiwoton@gmail.com>
To: selinux-refpolicy@vger.kernel.org
Subject: Access to raw memory: remove or make boolean?
Date: Mon, 24 Feb 2020 17:11:46 +0200 [thread overview]
Message-ID: <11011d01-844e-c526-a85f-92a7fc985d16@gmail.com> (raw)
Hi,
I made a PR 192 (https://github.com/SELinuxProject/refpolicy/pull/192)
for introducing a new boolean to disable access to raw memory devices
(/dev/mem, /dev/kmem, /dev/mergemem, dev/oldmem, /dev/port) because on
modern systems, direct access shouldn't be needed anymore. Chris
PeBenito asked to propose to this list whether instead of boolean, the
access should be removed unconditionally if it's no longer needed. I
think boolean could be useful for those systems where this is still
needed but still use latest reference policy.
-Topi Miettinen
next reply other threads:[~2020-02-24 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 15:11 Topi Miettinen [this message]
2020-02-24 15:42 ` Access to raw memory: remove or make boolean? Russell Coker
2020-02-24 15:56 ` Topi Miettinen
2020-02-25 0:27 ` Russell Coker
2020-02-25 8:54 ` Topi Miettinen
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=11011d01-844e-c526-a85f-92a7fc985d16@gmail.com \
--to=toiwoton@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).