Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (selinux-policy bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:6617
Description of problem: the following message appears in the systemd journal when any nsd-* program is executed as a cronjob. CROND[23753]: (root) CMDOUT (error: connect (/run/nsd/nsd.ctl): Permission denied) # matchpathcon /usr/sbin/nsd-* /usr/sbin/nsd-checkconf system_u:object_r:nsd_exec_t:s0 /usr/sbin/nsd-checkzone system_u:object_r:nsd_exec_t:s0 /usr/sbin/nsd-control system_u:object_r:nsd_exec_t:s0 /usr/sbin/nsd-control-setup system_u:object_r:nsd_exec_t:s0 # sesearch -c process -T | grep 'cron.*nsd_crond_t' type_transition crond_t nsd_exec_t:process nsd_crond_t; type_transition system_cronjob_t nsd_exec_t:process nsd_crond_t; # Version-Release number of selected component (if applicable): nsd-4.3.9-3.el9.x86_64 selinux-policy-38.1.12-1.el9.noarch selinux-policy-targeted-38.1.12-1.el9.noarch How reproducible: * always Steps to Reproduce: 1. get a RHEL-9.3 machine (targeted policy is active) 2. start the nsd service 3. add the following line into /etc/crontab file * * * * * nsd /usr/sbin/nsd-control status 4. restart the crond service 5. wait at least 1 minute 6. search for SELinux denials Actual results (enforcing mode): ---- type=PROCTITLE msg=audit(05/25/2023 07:23:01.953:1237) : proctitle=/usr/sbin/nsd-control status type=PATH msg=audit(05/25/2023 07:23:01.953:1237) : item=0 name=/run/nsd/nsd.ctl inode=1153 dev=00:18 mode=socket,755 ouid=nsd ogid=nsd rdev=00:00 obj=system_u:object_r:nsd_var_run_t:s0 nametype=NORMAL cap_fp=none cap_fi=none cap_fe=0 cap_fver=0 cap_frootid=0 type=CWD msg=audit(05/25/2023 07:23:01.953:1237) : cwd=/etc/nsd type=SOCKADDR msg=audit(05/25/2023 07:23:01.953:1237) : saddr={ saddr_fam=local path=/run/nsd/nsd.ctl } type=SYSCALL msg=audit(05/25/2023 07:23:01.953:1237) : arch=x86_64 syscall=connect success=no exit=EACCES(Permission denied) a0=0x3 a1=0x7ffc3b2cfdc0 a2=0x6e a3=0xfffffffffffffffc items=1 ppid=24462 pid=24474 auid=nsd uid=nsd gid=nsd euid=nsd suid=nsd fsuid=nsd egid=nsd sgid=nsd fsgid=nsd tty=(none) ses=96 comm=nsd-control exe=/usr/sbin/nsd-control subj=system_u:system_r:nsd_crond_t:s0-s0:c0.c1023 key=(null) type=AVC msg=audit(05/25/2023 07:23:01.953:1237) : avc: denied { write } for pid=24474 comm=nsd-control name=nsd.ctl dev="tmpfs" ino=1153 scontext=system_u:system_r:nsd_crond_t:s0-s0:c0.c1023 tcontext=system_u:object_r:nsd_var_run_t:s0 tclass=sock_file permissive=0 ---- Expected results: * no SELinux denials Additional info: * the nsd package comes from EPEL