From: Lukas Vrabec <lvrabec@redhat.com>
To: selinux@vger.kernel.org
Cc: Daniel J Walsh <dwalsh@redhat.com>
Subject: Container SELinux Customization tool - udica
Date: Thu, 15 Nov 2018 14:01:05 -0500 [thread overview]
Message-ID: <583686cd-d3e1-d7b6-fbe8-8ab4c26fa65d@redhat.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 877 bytes --]
Hi all,
Back in April, I announced that we work on POC how we could
automatically create SELinux security policies for different kind of
containers.
The original concept is described here:
https://github.com/fedora-selinux/container-selinux-customization
Long story short, using pre-defined policy blocks, system administrators
would be able to simply create customized SELinux policies for containers.
The goal is to create a standalone tool which would be able to do it.
It's called "udica" and you can find it here:
https://github.com/containers/udica
In this repo you can find sources and examples how to create SELinux
policy for your containers.
Udica is also available in Fedora repositories for Fedora Rawhide,
Fedora 29 and Fedora 28.
Feedback is welcome.
--
Lukas Vrabec
Software Engineer, Security Technologies
Red Hat, Inc.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2018-11-15 19:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=583686cd-d3e1-d7b6-fbe8-8ab4c26fa65d@redhat.com \
--to=lvrabec@redhat.com \
--cc=dwalsh@redhat.com \
--cc=selinux@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).