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.

Description of problem:

In FIPS mode, selinux prevents /usr/sbin/rndc to read urandom with the following AVC:

time->Thu Jul 10 11:56:41 2014
type=SYSCALL msg=audit(1405007801.451:984): arch=40000003 syscall=5 success=no exit=-13 a0=7e194a a1=900 a2=b775bcb8 a3=0 items=0 ppid=14077 pid=14080 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="rndc" exe="/usr/sbin/rndc" subj=unconfined_u:system_r:ndc_t:s0 key=(null)
type=AVC msg=audit(1405007801.451:984): avc:  denied  { read } for  pid=14080 comm="rndc" name="urandom" dev=devtmpfs ino=3913 scontext=unconfined_u:system_r:ndc_t:s0 tcontext=system_u:object_r:urandom_device_t:s0 tclass=chr_file

Version-Release number of selected component (if applicable):

selinux-policy-3.7.19-231.el6_5.3

How reproducible:

100%

Steps to Reproduce:

1. Execute the following test in FIPS mode:
   - /CoreOS/openssh/Security/bz1081343-openssh-failure-to-check-DNS-SSHFP-records-in

Actual results:

AVC found, test fails.

Expected results:

No AVC, test should pass.

Additional info:

Please notice that no such AVC is reported with FIPS mode disabled, aforementioned rndc call comes somewhere from bind-utils package (my guess is that it is called only in FIPS mode and that the issue can be reproduced simply by calling rndc).

Similar to BZ#1110397.

*** This bug has been marked as a duplicate of bug 1110397 ***