From: Daniel J Walsh <dwalsh@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@redhat.com>,
selinux@tycho.nsa.gov
Subject: Re: Strange AVC with latest rawhide kernel.
Date: Fri, 26 Feb 2016 14:42:47 -0500 [thread overview]
Message-ID: <1456515767.3481.48.camel@redhat.com> (raw)
In-Reply-To: <CAHC9VhRGwJVTcDrPF0KjA9haO5=tK_0w_eYXTxEMPSjH4NjDWA@mail.gmail.com>
On Fri, 2016-02-26 at 12:15 -0500, Paul Moore wrote:
> On Fri, Feb 26, 2016 at 11:31 AM, Daniel J Walsh <dwalsh@redhat.com>
> wrote:
> >
> > On Fri, 2016-02-26 at 10:46 -0500, Paul Moore wrote:
> > >
> > > Would that resolve all your problems Dan with Docker, runc, etc.?
> > > From our discussions the other day I thought you needed the
> > > ability
> > > transition to svirt_lxc_net_t from domains other than
> > > unconfined_t
> > > and docker_t ... or was I misunderstanding you?
> > Well the two ways we transition to svirt_sandbox_file_t is from
> > runc
> > which will usually from either docker_t or from unconfined_t. And
> > from
> > docker.
> >
> > We just need to label runc as docker_exec_t so that if you run it
> > from
> > a systemd unit file the correct transitions will happen.
> Okay, easy enough. Looks like we don't have to worry about this
> right now.
>
Although I will probably need to change the policy from docker_* to
containerapp_* since we will need to apply this policy to all tools
that launch containers. rkt, runc, docker, systemd-nspawn ...
next prev parent reply other threads:[~2016-02-26 19:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 18:02 Strange AVC with latest rawhide kernel Daniel J Walsh
2016-02-25 18:06 ` Stephen Smalley
2016-02-25 18:18 ` Stephen Smalley
2016-02-25 18:59 ` Daniel J Walsh
2016-02-25 19:12 ` Stephen Smalley
2016-02-25 19:36 ` Daniel J Walsh
2016-02-25 19:37 ` Eric Paris
2016-02-25 19:47 ` Stephen Smalley
2016-02-25 20:28 ` Daniel J Walsh
2016-02-25 20:54 ` Stephen Smalley
2016-02-26 12:54 ` Daniel J Walsh
2016-02-26 15:46 ` Paul Moore
2016-02-26 15:49 ` Stephen Smalley
2016-02-26 16:33 ` Daniel J Walsh
2016-02-26 19:50 ` James Carter
2016-02-26 20:30 ` Daniel J Walsh
2016-02-29 16:27 ` James Carter
2016-02-29 17:27 ` Daniel J Walsh
2016-02-26 17:13 ` Paul Moore
2016-02-26 19:41 ` Daniel J Walsh
2016-02-26 16:31 ` Daniel J Walsh
2016-02-26 17:15 ` Paul Moore
2016-02-26 19:42 ` Daniel J Walsh [this message]
2016-02-25 20:36 ` Daniel J Walsh
2016-02-29 10:10 ` Miroslav Grepl
2016-02-25 19:25 ` Daniel J Walsh
2016-02-25 19:05 ` Paul Moore
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=1456515767.3481.48.camel@redhat.com \
--to=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.