SELinux-Refpolicy Archive on lore.kernel.org
 help / color / Atom feed
* Access to raw memory: remove or make boolean?
@ 2020-02-24 15:11 Topi Miettinen
  2020-02-24 15:42 ` Russell Coker
  0 siblings, 1 reply; 5+ messages in thread
From: Topi Miettinen @ 2020-02-24 15:11 UTC (permalink / raw)
  To: selinux-refpolicy

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, back to index

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-24 15:11 Access to raw memory: remove or make boolean? Topi Miettinen
2020-02-24 15:42 ` Russell Coker
2020-02-24 15:56   ` Topi Miettinen
2020-02-25  0:27     ` Russell Coker
2020-02-25  8:54       ` Topi Miettinen

SELinux-Refpolicy Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/selinux-refpolicy/0 selinux-refpolicy/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 selinux-refpolicy selinux-refpolicy/ https://lore.kernel.org/selinux-refpolicy \
		selinux-refpolicy@vger.kernel.org
	public-inbox-index selinux-refpolicy

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.selinux-refpolicy


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git