Red Hat Bugzilla – Bug 129106
Mistake in documentation concerning Securing NIS
Last modified: 2014-08-04 18:15:00 EDT
Description of problem:
The documentation that shows how to create a secure NIS server is
incorrect. The documentation does not make the NIS server use static
ports. I have found a fix to the problem and it is quite easy to
make the change to the documentation. In the section titled "5.3.4.
Assign Static Ports and Use IPTables Rules" it says to change
the /etc/sysconfig/network file in order to allow static ports for
NIS. The documentation at this moment says that the two lines
should be added to the file to create the static ports. I tried to
get it working under this change and could not. But I found that the
simple change of editing those new lines to be
will create the desired effect. Just to let you know.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
reassigning to mainatiner.
hi David, please check the relevance of this in regards to where we are with
emailed firstname.lastname@example.org for validation.
The following comment from email@example.com:
From the ypserv man page:
-p --port port
ypserv will bind itself to this port. This makes it possible to
have a router filter packets to the NIS ports, so that access to
the NIS server from hosts on the Internet can be restricted.
From the rpc.ypxfrd man page:
rpc.ypxfrd will bind itself to this port, which makes it possi-
ble to have a router filter packets to the NIS ports. This can
restrict the access to the NIS server from hosts on the Inter-
So I do not think that it is a good idea to change YPXFRD_ARGS to
"--port 835", because rpc.ypxfrd does not accept --port as an option.
I'm not changing the doc for the present. I'll try to get someone to actually
test this and validate what works and what doesn't.
Adding 'cc firstname.lastname@example.org for tracking
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.