From: bigon@debian.org (Laurent Bigonville)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Transition not working as expected with boolean cron_userdomain_transition set to on
Date: Mon, 23 Nov 2015 13:15:07 +0100 [thread overview]
Message-ID: <5653034B.3010607@debian.org> (raw)
In-Reply-To: <20151123120014.GA826@x250>
Le 23/11/15 13:00, Dominick Grift a ?crit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On Mon, Nov 23, 2015 at 12:31:00PM +0100, Laurent Bigonville wrote:
>> [...]
>>
>>
>> When cron_userdomain_transition boolean is set to on, the user cronjobs
>> are supposed to run in their domains. Without this patch the default
>> context is not properly computed:
>>
>> $ /usr/sbin/getdefaultcon user_u system_u:system_r:crond_t:s0
>> /usr/sbin/getdefaultcon: Invalid argument
>> $ /usr/sbin/getdefaultcon staff_u system_u:system_r:crond_t:s0
>> staff_u:sysadm_r:sysadm_t:s0
> this is not a accurate description since it expects a user name and not a
> selinux user id (right?)
>
>> With this patch applied:
>>
>> $ /usr/sbin/getdefaultcon user_u system_u:system_r:crond_t:s0
>> user_u:user_r:user_t:s0
>> $ /usr/sbin/getdefaultcon staff_ system_u:system_r:crond_t:s0
>> staff_u:staff_r:staff_t:s0
> idem ditto
Yes indeed, it was to make the thing more clear for the reader
next prev parent reply other threads:[~2015-11-23 12:15 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 [this message]
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
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=5653034B.3010607@debian.org \
--to=bigon@debian.org \
--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.