Bug 760473 - sVirt allows PROT_EXEC mappings
Summary: sVirt allows PROT_EXEC mappings
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 750284
TreeView+ depends on / blocked
 
Reported: 2011-12-06 09:46 UTC by Jiri Denemark
Modified: 2013-01-09 11:57 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 750284
Environment:
Last Closed: 2012-10-15 18:27:21 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Comment 2 Miroslav Grepl 2011-12-09 12:11:01 UTC 
Jiri, 
how are you planning to set a context?
Comment 7 Jiri Denemark 2012-01-17 09:24:44 UTC 
(In reply to comment #2)
> Jiri, 
> how are you planning to set a context?

Oops, sorry for such late reply. Libvirt already sets the context using setexeccon() just before exec()ing qemu-kvm binary. However, currently we use the context we get from reading selinux_virtual_domain_context_path() and we'd probably need similar thing for the new context to avoid hardcoding it in libvirt itself.
Comment 9 RHEL Program Management 2012-05-03 05:20:25 UTC 
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Note You need to log in before you can comment on or make changes to this bug.