[yocto] No SELinux security context (/etc/crontab)

Mark Hatle mark.hatle at kernel.crashing.org
Mon Oct 14 07:29:52 PDT 2019


There SE Linux policy included in meta-selinux is just a starting point.  It's
expected that you will have to update/customize it.

With that said, these types of issues, we will accept patches for them.

--Mark

On 10/10/19 5:06 AM, Oriya, Raxesh wrote:
> Hi,
> 
>  
> 
> I have enabled SELinux in my yocto project(warrior branch) but *cron *is not
> functioning because of some SELinux context isuue. I am using *minimum* SELinux
> policy. Here is the error from `/var/log/messages`
> 
>  
> 
>     Oct  9 04:50:01 panther2 cron.info crond[261]: ((null)) No SELinux security
> context (/etc/crontab)       
> 
>     Oct  9 04:50:01 panther2 cron.info crond[261]: (root) FAILED (loading cron
> table)                      
> 
>  
> 
> Here are some contexts for relevant files,
> 
>  
> 
>     root at panther2:~# ps -efZ | grep cron
> 
>     system_u:system_r:kernel_t:s0   root       464     1  0 04:54 ?    00:00:00
> /usr/sbin/crond -n
> 
>  
> 
>     root at panther2:~# ls -lZ /etc/crontab
> 
>     -rw-------. 1 root root system_u:object_r:unconfined_t:s0 653 Oct  9  2019
> /etc/crontab
> 
>  
> 
>     root at panther2:~# ls -lZ /usr/sbin/crond
> 
>     -rwxr-xr-x. 1 root root system_u:object_r:unlabeled_t:s0 68160 Oct  9  2019
> /usr/sbin/crond
> 
>  
> 
> Any help? Thanks !!
> 
>  
> 
> Regards,
> 
> Thanks
> 
> 


More information about the yocto mailing list