Blame SOURCES/nfs-utils-2.3.3-man-tcpwrappers.patch

381c0b
diff -up nfs-utils-2.5.4/utils/mountd/mountd.man.orig nfs-utils-2.5.4/utils/mountd/mountd.man
381c0b
--- nfs-utils-2.5.4/utils/mountd/mountd.man.orig	2022-01-22 16:56:29.715967394 -0500
381c0b
+++ nfs-utils-2.5.4/utils/mountd/mountd.man	2022-01-22 16:57:07.494103095 -0500
381c0b
@@ -291,36 +291,7 @@ section include
381c0b
 which each have the same meaning as given by
381c0b
 .BR rpc.nfsd (8).
381c0b
 
381c0b
-.SH TCP_WRAPPERS SUPPORT
381c0b
-You can protect your
381c0b
-.B rpc.mountd
381c0b
-listeners using the
381c0b
-.B tcp_wrapper
381c0b
-library or
381c0b
-.BR iptables (8).
381c0b
-.PP
381c0b
-Note that the
381c0b
-.B tcp_wrapper
381c0b
-library supports only IPv4 networking.
381c0b
-.PP
381c0b
-Add the hostnames of NFS peers that are allowed to access
381c0b
-.B rpc.mountd
381c0b
-to
381c0b
-.IR /etc/hosts.allow .
381c0b
-Use the daemon name
381c0b
-.B mountd
381c0b
-even if the
381c0b
-.B rpc.mountd
381c0b
-binary has a different name.
381c0b
-.PP
381c0b
-Hostnames used in either access file will be ignored when
381c0b
-they can not be resolved into IP addresses.
381c0b
-For further information see the
381c0b
-.BR tcpd (8)
381c0b
-and
381c0b
-.BR hosts_access (5)
381c0b
-man pages.
381c0b
-.SS IPv6 and TI-RPC support
381c0b
+.SH IPv6 and TI-RPC support
381c0b
 TI-RPC is a pre-requisite for supporting NFS on IPv6.
381c0b
 If TI-RPC support is built into
381c0b
 .BR rpc.mountd ,
381c0b
@@ -347,7 +318,6 @@ table of clients accessing server's expo
381c0b
 .BR nfs (5),
381c0b
 .BR nfs.conf (5),
381c0b
 .BR tcpd (8),
381c0b
-.BR hosts_access (5),
381c0b
 .BR iptables (8),
381c0b
 .BR netconfig (5)
381c0b
 .sp
381c0b
diff -up nfs-utils-2.5.4/utils/statd/statd.man.orig nfs-utils-2.5.4/utils/statd/statd.man
381c0b
--- nfs-utils-2.5.4/utils/statd/statd.man.orig	2022-01-22 16:56:29.718967405 -0500
381c0b
+++ nfs-utils-2.5.4/utils/statd/statd.man	2022-01-22 16:57:07.495103099 -0500
381c0b
@@ -325,28 +325,6 @@ chooses, simply use
381c0b
 .BR chown (1)
381c0b
 to set the owner of
381c0b
 the state directory.
381c0b
-.PP
381c0b
-You can also protect your
381c0b
-.B rpc.statd
381c0b
-listeners using the
381c0b
-.B tcp_wrapper
381c0b
-library or
381c0b
-.BR iptables (8).
381c0b
-To use the
381c0b
-.B tcp_wrapper
381c0b
-library, add the hostnames of peers that should be allowed access to
381c0b
-.IR /etc/hosts.allow .
381c0b
-Use the daemon name
381c0b
-.B statd
381c0b
-even if the
381c0b
-.B rpc.statd
381c0b
-binary has a different filename.
381c0b
-.P
381c0b
-For further information see the
381c0b
-.BR tcpd (8)
381c0b
-and
381c0b
-.BR hosts_access (5)
381c0b
-man pages.
381c0b
 .SH ADDITIONAL NOTES
381c0b
 Lock recovery after a reboot is critical to maintaining data integrity
381c0b
 and preventing unnecessary application hangs.
381c0b
@@ -451,7 +429,6 @@ network transport capability database
381c0b
 .BR rpc.nfsd (8),
381c0b
 .BR rpcbind (8),
381c0b
 .BR tcpd (8),
381c0b
-.BR hosts_access (5),
381c0b
 .BR iptables (8),
381c0b
 .BR netconfig (5)
381c0b
 .sp