From: Kenton Groombridge <me@concord.sh>
To: selinux-refpolicy@vger.kernel.org
Subject: [RFC] containers module in refpolicy
Date: Wed, 11 Aug 2021 18:07:28 -0400 [thread overview]
Message-ID: <20210811220728.erzu5drv6zlh2tpg@bubbles> (raw)
At this time refpolicy does not have much (if any) support for various
container runtimes such as docker or podman. An issue was raised on
container-selinux[1] about the possibility of allowing it to be built
against refpolicy, but the question came up of whether or not it would
be a better idea to instead introduce such a module specifically in
refpolicy. Upstream seems to be open to the idea of making
container-selinux work with refpolicy, but I worry that the task of
maintaining the module will be more work in the long run.
What are your thoughts?
next reply other threads:[~2021-08-11 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 22:07 Kenton Groombridge [this message]
2021-08-12 5:22 ` [RFC] containers module in refpolicy Russell Coker
2021-08-12 11:55 ` Kenton Groombridge
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=20210811220728.erzu5drv6zlh2tpg@bubbles \
--to=me@concord.sh \
--cc=selinux-refpolicy@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 read-only IMAP folder(s) and NNTP newsgroup(s).