From: yangshukui@huawei.com (yangshukui)
To: linux-security-module@vger.kernel.org
Subject: isolate selinux_enforcing
Date: Thu, 9 Mar 2017 17:03:40 +0800 [thread overview]
Message-ID: <58C11A6C.7000408@huawei.com> (raw)
In-Reply-To: <58736B2E.90201@huawei.com>
I want to use SELinux in system container and only concern the function
in the container.
this system container run in vm and every vm has only one system container.
How do I use now?
docker run ... system-contaier /sbin/init
after init is running ,the following service is also running:
#this is the part of service file which will run in container after
starting the container.
...
semodule -R #use the policy in container.
restorecon / #if needed
...
this method seem to work if host os and the docker images use the same
content for rootfs, but if host use
redhat7 and docker images use centos7, it will deny many normal
operations , and this let some host service not work.
If SELinux is permissive in host and enforcing in container ,it will
resolve my problem. Unfortunately,
there is no namespace for SELinux.
Isolate SELinux is difficult and it has a lot of work to do, but is
easier to isolate selinux_enforcing.
What do you think ?
Think you very much.
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2017-03-09 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58732BCF.4090908@huawei.com>
[not found] ` <58734284.1060504@huawei.com>
[not found] ` <b7f75f65-592a-5102-0ac5-4d3aa43f0b55@huawei.com>
[not found] ` <58736B2E.90201@huawei.com>
2017-03-09 9:03 ` yangshukui [this message]
2017-03-09 15:28 ` isolate selinux_enforcing Stephen Smalley
2017-03-09 15:39 ` Stephen Smalley
2017-03-09 16:39 ` Casey Schaufler
2017-03-09 20:49 ` Eric W. Biederman
2017-03-10 0:05 ` Paul Moore
2017-03-13 7:06 ` James Morris
2017-03-13 16:05 ` Casey Schaufler
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=58C11A6C.7000408@huawei.com \
--to=yangshukui@huawei.com \
--cc=linux-security-module@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 NNTP newsgroup(s).