Created attachment 360786 [details] relocate pidfile Description of problem: The init script of dkim-milter touches /var/run/dkim-milter.pid and then chown's the file. Creating a SELinux policy is really hard in such a case because the file gets labeled as initrc_var_run_t but would need a type transition to milter_dkim_data_t. To solve this couldn't we write the pid file to /var/run/dkim-milter/dkim-milter.pid? This directory is owned by dkim-milter and therefore already writeable for the unprivileged user. This would solve the problem with SELinux policy writing and shouldn't hurt.
dkim-milter-2.8.3-3.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/dkim-milter-2.8.3-3.el5
dkim-milter-2.8.3-3.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/dkim-milter-2.8.3-3.fc11
dkim-milter-2.8.3-3.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/dkim-milter-2.8.3-3.fc10
Version dkim-milter-2.8.3-3 works fine. Thanks + Closed.
dkim-milter-2.8.3-3.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
dkim-milter-2.8.3-3.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
dkim-milter-2.8.3-3.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.