From: serue@us.ibm.com (Serge E. Hallyn)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] container policy interface
Date: Wed, 10 Dec 2008 16:03:51 -0600 [thread overview]
Message-ID: <20081210220351.GA22448@us.ibm.com> (raw)
In-Reply-To: <493FE28C.5060602@redhat.com>
Quoting Daniel J Walsh (dwalsh at redhat.com):
> Interesting idea, although I have never used containers.
>
> Rather then specifying unconfined_t and staff_t I think it would be
> better to define an attribute
Thanks Dan, I'll apply these and test in the next few days.
-serge
next prev parent reply other threads:[~2008-12-10 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 20:37 [refpolicy] container policy interface Serge E. Hallyn
2008-12-09 23:33 ` Serge E. Hallyn
2008-12-10 15:38 ` Daniel J Walsh
2008-12-10 22:03 ` Serge E. Hallyn [this message]
2008-12-22 17:11 ` Serge E. Hallyn
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=20081210220351.GA22448@us.ibm.com \
--to=serue@us.ibm.com \
--cc=refpolicy@oss.tresys.com \
/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.