Bug#857662: cron broken in SELinux enforced mode due to system_u login mapping removal

2017-12-05 Thread Laurent Bigonville
On Mon, 13 Mar 2017 21:09:13 +0100 cgzones wrote: > Hi, Hello, > with the removal of the SELinux login entry for system_u [1], cron > stops working. > > get_security_context [2] expects a NULL name when called for a system cronjob. > But it is called with "system_u"

Bug#857662: cron broken in SELinux enforced mode due to system_u login mapping removal

2017-10-03 Thread Laurent Bigonville
tag 857662 + patch thanks On Mon, 13 Mar 2017 21:09:13 +0100 cgzones wrote: > Hi, > with the removal of the SELinux login entry for system_u [1], cron > stops working. > > get_security_context [2] expects a NULL name when called for a system cronjob. > But it is

Bug#857662: cron broken in SELinux enforced mode due to system_u login mapping removal

2017-03-13 Thread cgzones
Package: cron Version: 3.0pl1-128+b1 User: selinux-de...@lists.alioth.debian.org Usertags: selinux Hi, with the removal of the SELinux login entry for system_u [1], cron stops working. get_security_context [2] expects a NULL name when called for a system cronjob. But it is called with "system_u"