All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] apps_livecd.patch
Date: Tue, 21 Jul 2009 10:44:12 -0400	[thread overview]
Message-ID: <4A65D43C.1010100@redhat.com> (raw)
In-Reply-To: <1248185504.2914.443.camel@gorn.columbia.tresys.com>

On 07/21/2009 10:11 AM, Christopher J. PeBenito wrote:
> On Thu, 2009-05-21 at 09:55 -0400, Daniel J Walsh wrote:
>> http://people.fedoraproject.org/~dwalsh/SELinux/F11/apps_livecd.patch
>>
>> Policy for the livecd command, allows the creation of images for
>> different OS Versions then the host machine.
> 
> I don't understand why this needs its own policy.
> 
livecd policy is used to allow it to apply labels that the host machine does not understand.  So if I am running livecd on a F10 box, and I want to build a livecd for F11, livecd will write context that F10 does not understand.  It should be the only process allowed to write these labels.

seutil_domtrans_setfiles_mac(livecd_t)

Is the key.

  reply	other threads:[~2009-07-21 14:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 13:55 [refpolicy] apps_livecd.patch Daniel J Walsh
2009-07-21 14:11 ` Christopher J. PeBenito
2009-07-21 14:44   ` Daniel J Walsh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-26 22:38 Daniel J Walsh
2010-06-02 20:07 Daniel J Walsh
2010-07-07 14:29 ` Christopher J. PeBenito
2010-07-07 14:31   ` Dominick Grift
2010-07-12 14:43     ` Daniel J Walsh
2010-07-12 14:51       ` Dominick Grift
2010-07-12 17:33         ` Daniel J Walsh
2010-02-23 19:27 Daniel J Walsh
2009-11-12 20:46 Daniel J Walsh
2009-08-28 20:07 Daniel J Walsh
2009-09-10 13:09 ` Christopher J. PeBenito
2009-03-04 21:39 Daniel J Walsh

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=4A65D43C.1010100@redhat.com \
    --to=dwalsh@redhat.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.