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:
This bz was opened to discuss the following AVC denial caused by kpropd after it got its own selinux doamin.

----
type=SYSCALL msg=audit(05/26/2015 10:57:12.380:460) : arch=x86_64 syscall=connect success=yes exit=0 a0=0x4 a1=0x7f23d0a28ae0 a2=0x1c a3=0x7ffd32d0d900 items=0 ppid=1 pid=12967 auid=root uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=(none) ses=55 comm=kpropd exe=/usr/sbin/kpropd subj=unconfined_u:system_r:kpropd_t:s0 key=(null) 
type=AVC msg=audit(05/26/2015 10:57:12.380:460) : avc:  denied  { name_connect } for  pid=12967 comm=kpropd dest=272 scontext=unconfined_u:system_r:kpropd_t:s0 tcontext=system_u:object_r:reserved_port_t:s0 tclass=tcp_socket 


The main question here is what kpropd is trying to do here.


Version-Release number of selected component (if applicable):
krb5-libs-1.10.3-42.el6.x86_64
selinux-policy-3.7.19-269.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. Set up incremental pripagation
(should you need more detail, feel free to ask)

Actual results:
AVC denial are logged and the propagation fails

Expected results:
no AVC denials and the propagation is working

To me this looks like a normal operation: kpropd initiate a connection to kadmind via TCP:272 that should be allowed.

Is this anything new?

(In reply to Miroslav Grepl from comment #4)
> Is this anything new?

As far as I know not, it's here for some time already.
@Roland, can you confirm, plase?

We just had no test for it + it run in unconfined domain, so it was not noticed.