All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Transition not working as expected with boolean cron_userdomain_transition set to on
Date: Thu, 3 Dec 2015 10:57:08 -0500	[thread overview]
Message-ID: <56606654.5070208@tresys.com> (raw)
In-Reply-To: <566052B2.4050401@debian.org>

On 12/3/2015 9:33 AM, Laurent Bigonville wrote:
> Le 02/12/15 15:35, Christopher J. PeBenito a ?crit :
>> On 12/1/2015 11:26 AM, Laurent Bigonville wrote:
>>> Le 01/12/15 16:50, Christopher J. PeBenito a ?crit :
>>>> This makes sense, though the default_context files should probably
>>>> be updated similarly. 
>>> Is the order relevant here?
>> For each line, the order is relevant.  The libraries will choose the
>> first partial context that will result in a valid context.  I'd have to
>> look at the code to see if it will skip partial contexts if the context
>> is valid but the transition is denied.
> And in this precise case, do you have a specific order for these
> contexts in the default_contexts file?

I think it should be like the user default_context files, where the user
domains are first, so those are chosen if the cron_userdomain_transition
is true.  If false, then it should fall through to the cronjob domains.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

      reply	other threads:[~2015-12-03 15:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 11:31 [refpolicy] Transition not working as expected with boolean cron_userdomain_transition set to on Laurent Bigonville
2015-11-23 12:00 ` Dominick Grift
2015-11-23 12:15   ` Laurent Bigonville
2015-11-23 12:39     ` Dominick Grift
2015-12-01 15:50 ` Christopher J. PeBenito
2015-12-01 16:26   ` Laurent Bigonville
2015-12-02 14:35     ` Christopher J. PeBenito
2015-12-03 14:33       ` Laurent Bigonville
2015-12-03 15:57         ` Christopher J. PeBenito [this message]

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=56606654.5070208@tresys.com \
    --to=cpebenito@tresys.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.