From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: refpolicy@oss.tresys.com
Cc: xen-devel@lists.xenproject.org
Subject: [refpolicy SELinux PATCH] Updates to SELinux refpolicies to make xenconsoled work. (v1)]
Date: Mon, 9 Oct 2017 12:53:43 -0400 [thread overview]
Message-ID: <20171009165342.GC9212@localhost.localdomain> (raw)
Re-sending as the first didn't hit the refpolicy mailing list.
Date: Mon, 9 Oct 2017 11:53:45 -0400
From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: refpolicy@oss.tresys.com
Cc: xen-devel@lists.xenproject.org
Subject: [refpolicy SELinux PATCH] Updates to SELinux refpolicies to make
xenconsoled work. (v1)
Hey!
Since Xen 4.6 the xenstored prefers to use /dev/xen/xenbus instead of /proc/xen/xenbus.
That wasn't in the original email that Anthony had sent:
"[refpolicy] [SELINUX POLICY PATCH] Update for Xen 4.7"
http://oss.tresys.com/pipermail/refpolicy/2017-August/009784.html
But nonetheless it is needed to make xenconsoled work on Fedora installs.
Additionally we also add the 'map' functionality to make the xenconsoled
/xenconsole work together.
For more details, please see:
https://bugzilla.redhat.com/show_bug.cgi?id=1484908
Please merge at your convience.
Konrad Rzeszutek Wilk (2):
kernel/xen: Update for Xen 4.6
kernel/xen: Add map permission to the dev_rw_xen
policy/modules/kernel/devices.fc | 1 +
policy/modules/kernel/devices.if | 1 +
2 files changed, 2 insertions(+)
----- End forwarded message -----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-10-09 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 16:53 Konrad Rzeszutek Wilk [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-09 15:53 [refpolicy SELinux PATCH] Updates to SELinux refpolicies to make xenconsoled work. (v1) Konrad Rzeszutek Wilk
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=20171009165342.GC9212@localhost.localdomain \
--to=konrad@kernel.org \
--cc=refpolicy@oss.tresys.com \
--cc=xen-devel@lists.xenproject.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).