Description of problem: When a process with context 'unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023' creates the '/root/.esmtp_queue/' directory, then the directory is assigned the correct context 'unconfined_u:object_r:mail_home_rw_t:s0' However, if the process that creates the directory has context 'system_u:system_r:crond_t:s0-s0:c0.c1023' (context of the 'atd' daemon - note that this context is only preserved, when 'atd' is sending mail internally. The context is set to unconfined when running the jobs.) or 'system_u:system_r:system_cronjob_t:s0-s0:c0.c1023' (context of a regular cron job) then the created directory has incorrect context 'system_u:object_r:admin_home_t:s0' Version-Release number of selected component (if applicable): selinux-policy-3.13.1-158.21.fc23
This might be the cause of [1] and [2], but there may be other process contexts, under which the directory is created with bad context. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1282043 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1319370
*** Bug 1282043 has been marked as a duplicate of this bug. ***
*** Bug 1319370 has been marked as a duplicate of this bug. ***
(In reply to Ondřej Lysoněk from comment #0) > When a process with context > 'unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023' > creates the '/root/.esmtp_queue/' directory, then the directory is assigned > the correct context N.B. I'm seeing atd use /.esmtp_queue/ **not** /root/.esmtp_queue/
(In reply to Jonathan Wakely from comment #4) > (In reply to Ondřej Lysoněk from comment #0) > > When a process with context > > 'unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023' > > creates the '/root/.esmtp_queue/' directory, then the directory is assigned > > the correct context > > N.B. I'm seeing atd use /.esmtp_queue/ **not** /root/.esmtp_queue/ Yes, this is a bug, which is being resolved in [1]. The correct directory should be /root/.esmtp_queue/. If you want to test this bug, I can send you a patch for esmtp, which fixes [1]. I did not build it yet, as I'm waiting for the resolution of this selinux-policy bug. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1303305
This seems to be fixed now in f24-rawhide. Are you planning to backport the fix to f23 too?
It's backported. I just need to create new build.
selinux-policy-3.13.1-158.24.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-f739cc7524
selinux-policy-3.13.1-158.24.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-f739cc7524
selinux-policy-3.13.1-158.24.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.