Bug 1135763 - missing policy for secure containers
Summary: missing policy for secure containers
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-31 10:46 UTC by Gene Czarcinski
Modified: 2023-09-14 02:46 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:20:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
updates supporting secure container (653 bytes, text/plain)
2014-08-31 10:46 UTC, Gene Czarcinski
no flags Details

Description Gene Czarcinski 2014-08-31 10:46:13 UTC
Created attachment 933094 [details]
updates supporting secure container

Description of problem:
Selinux policy rulles for secure contailers (virt-sandbox-service) are missing.

1. Needed the following executed:
    setsebool virt_sandbox_use_sys_admin 1
    setsebool virt_sandbox_use_all_caps 1
    setsebool -P virt_sandbox_use_netlink 1

2. Also needed the attached file for semanage -i



Version-Release number of selected component (if applicable):
Fedora 20 updated, fedora-virt-preview

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Daniel Walsh 2014-08-31 10:57:33 UTC
It looks like you only needed

allow systemd_logind_t virtd_lxc_t:dbus send_msg;

with those booleans set?

Comment 2 Gene Czarcinski 2014-08-31 12:00:30 UTC
When I first started using secure containers I got the selinux hit plus messages about setsebool in /var/log/messages.  So I ran audit2allow and then did the setsebool commands too.

Is this "corrected" in F21 or is this a problem there too? [not that I am getting very far on F21 because of BZ #1135762]

Comment 3 Fedora End Of Life 2015-05-29 12:46:25 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Daniel Walsh 2015-05-29 13:06:47 UTC
Gene, are you still having problems?

Comment 5 Fedora End Of Life 2015-06-29 22:20:39 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Red Hat Bugzilla 2023-09-14 02:46:42 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.