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.
Description of problem:
We run RHEL 6.1 on a NIS master with two other machines running as NIS slaves.
The NIS master runs "yppasswdd --port 836". When a NIS client changes a NIS password, the updated password is written to the passwd file, yppasswdd calls "make" in /var/yp, the local passwd.byname and passwd.byuid databases are rebuilt, but they are not pushed to the NIS slaves. Instead the following message is logged:
kernel: type=1400 audit(1363998232.751:20728): avc: denied { name_connect } for pid=9739 comm="yppush" dest=111 scontext=system_u:system_r:yppasswdd_t:s0 tcontext=system_u:object_r:portmap_port_t:s0 tclass=tcp_socket
Obviously, yppush when called from yppasswdd is not allowed to connect to the rpcbind daemon. I have been able to "fix" this with a local SElinux rule:
allow yppasswdd_t portmap_port_t:tcp_socket name_connect;
Unfortunately, it still does not work, another avc is logged:
kernel: type=1400 audit(1364055250.719:22259): avc: denied { name_connect } for pid=11586 comm="yppush" dest=804 scontext=unconfined_u:system_r:yppasswdd_t:s0 tcontext=system_u:object_r:hi_reserved_port_t:s0 tclass=tcp_socket
With a second local SElinux rule, everything works:
allow yppasswdd_t hi_reserved_port_t:tcp_socket name_connect;
Please update selinux-policy to allow yppasswdd/yppush to push NIS maps to the slaves, either with the abovementioned allows or a different approach.
Version-Release number of selected component (if applicable):
I have observed the problem with 3.7.19-93, but don't think it is fixed in the current -195.
How reproducible: always
Steps to Reproduce:
1. Set up NIS master server with at least one NIS slave, run yppasswdd daemon on NIS master.
2. Enable yppush in /var/yp/Makefile:
NOPUSH=false
3. On a NIS client, change the passwd of the user.
Actual results:
4. The new password is updated on the NIS master's passwd/shadow file and the database, but not on the slave server(s). Observe abovementioned error message(s) on NIS master.
Expected results:
5. The password is also updated on the slaves, no avc error in log.
Additional info:
# cat mypol.te
policy_module(mypol, 1.0)
require{
type yppasswdd_t;
}
nis_use_ypbind(yppasswdd_t)
# make -f /usr/share/selinux/devel/Makefile mypol.pp
# semodule -i mypol.pp
will fix it for now.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-1598.html
Description of problem: We run RHEL 6.1 on a NIS master with two other machines running as NIS slaves. The NIS master runs "yppasswdd --port 836". When a NIS client changes a NIS password, the updated password is written to the passwd file, yppasswdd calls "make" in /var/yp, the local passwd.byname and passwd.byuid databases are rebuilt, but they are not pushed to the NIS slaves. Instead the following message is logged: kernel: type=1400 audit(1363998232.751:20728): avc: denied { name_connect } for pid=9739 comm="yppush" dest=111 scontext=system_u:system_r:yppasswdd_t:s0 tcontext=system_u:object_r:portmap_port_t:s0 tclass=tcp_socket Obviously, yppush when called from yppasswdd is not allowed to connect to the rpcbind daemon. I have been able to "fix" this with a local SElinux rule: allow yppasswdd_t portmap_port_t:tcp_socket name_connect; Unfortunately, it still does not work, another avc is logged: kernel: type=1400 audit(1364055250.719:22259): avc: denied { name_connect } for pid=11586 comm="yppush" dest=804 scontext=unconfined_u:system_r:yppasswdd_t:s0 tcontext=system_u:object_r:hi_reserved_port_t:s0 tclass=tcp_socket With a second local SElinux rule, everything works: allow yppasswdd_t hi_reserved_port_t:tcp_socket name_connect; Please update selinux-policy to allow yppasswdd/yppush to push NIS maps to the slaves, either with the abovementioned allows or a different approach. Version-Release number of selected component (if applicable): I have observed the problem with 3.7.19-93, but don't think it is fixed in the current -195. How reproducible: always Steps to Reproduce: 1. Set up NIS master server with at least one NIS slave, run yppasswdd daemon on NIS master. 2. Enable yppush in /var/yp/Makefile: NOPUSH=false 3. On a NIS client, change the passwd of the user. Actual results: 4. The new password is updated on the NIS master's passwd/shadow file and the database, but not on the slave server(s). Observe abovementioned error message(s) on NIS master. Expected results: 5. The password is also updated on the slaves, no avc error in log. Additional info: