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

bc9fd4
diff -up nfs-utils-2.3.3/utils/mountd/mountd.man.orig nfs-utils-2.3.3/utils/mountd/mountd.man
bc9fd4
--- nfs-utils-2.3.3/utils/mountd/mountd.man.orig	2018-09-06 14:09:08.000000000 -0400
bc9fd4
+++ nfs-utils-2.3.3/utils/mountd/mountd.man	2018-10-26 09:53:10.005127368 -0400
bc9fd4
@@ -232,36 +232,7 @@ section include
bc9fd4
 which each have same same meaning as given by
bc9fd4
 .BR rpc.nfsd (8).
bc9fd4
 
bc9fd4
-.SH TCP_WRAPPERS SUPPORT
bc9fd4
-You can protect your
bc9fd4
-.B rpc.mountd
bc9fd4
-listeners using the
bc9fd4
-.B tcp_wrapper
bc9fd4
-library or
bc9fd4
-.BR iptables (8).
bc9fd4
-.PP
bc9fd4
-Note that the
bc9fd4
-.B tcp_wrapper
bc9fd4
-library supports only IPv4 networking.
bc9fd4
-.PP
bc9fd4
-Add the hostnames of NFS peers that are allowed to access
bc9fd4
-.B rpc.mountd
bc9fd4
-to
bc9fd4
-.IR /etc/hosts.allow .
bc9fd4
-Use the daemon name
bc9fd4
-.B mountd
bc9fd4
-even if the
bc9fd4
-.B rpc.mountd
bc9fd4
-binary has a different name.
bc9fd4
-.PP
bc9fd4
-Hostnames used in either access file will be ignored when
bc9fd4
-they can not be resolved into IP addresses.
bc9fd4
-For further information see the
bc9fd4
-.BR tcpd (8)
bc9fd4
-and
bc9fd4
-.BR hosts_access (5)
bc9fd4
-man pages.
bc9fd4
-.SS IPv6 and TI-RPC support
bc9fd4
+.SH IPv6 and TI-RPC support
bc9fd4
 TI-RPC is a pre-requisite for supporting NFS on IPv6.
bc9fd4
 If TI-RPC support is built into
bc9fd4
 .BR rpc.mountd ,
bc9fd4
@@ -288,7 +259,6 @@ table of clients accessing server's expo
bc9fd4
 .BR nfs (5),
bc9fd4
 .BR nfs.conf (5),
bc9fd4
 .BR tcpd (8),
bc9fd4
-.BR hosts_access (5),
bc9fd4
 .BR iptables (8),
bc9fd4
 .BR netconfig (5)
bc9fd4
 .sp
bc9fd4
diff -up nfs-utils-2.3.3/utils/statd/statd.man.orig nfs-utils-2.3.3/utils/statd/statd.man
bc9fd4
--- nfs-utils-2.3.3/utils/statd/statd.man.orig	2018-10-26 09:52:27.609358805 -0400
bc9fd4
+++ nfs-utils-2.3.3/utils/statd/statd.man	2018-10-26 09:53:37.345978117 -0400
bc9fd4
@@ -319,28 +319,6 @@ chooses, simply use
bc9fd4
 .BR chown (1)
bc9fd4
 to set the owner of
bc9fd4
 the state directory.
bc9fd4
-.PP
bc9fd4
-You can also protect your
bc9fd4
-.B rpc.statd
bc9fd4
-listeners using the
bc9fd4
-.B tcp_wrapper
bc9fd4
-library or
bc9fd4
-.BR iptables (8).
bc9fd4
-To use the
bc9fd4
-.B tcp_wrapper
bc9fd4
-library, add the hostnames of peers that should be allowed access to
bc9fd4
-.IR /etc/hosts.allow .
bc9fd4
-Use the daemon name
bc9fd4
-.B statd
bc9fd4
-even if the
bc9fd4
-.B rpc.statd
bc9fd4
-binary has a different filename.
bc9fd4
-.P
bc9fd4
-For further information see the
bc9fd4
-.BR tcpd (8)
bc9fd4
-and
bc9fd4
-.BR hosts_access (5)
bc9fd4
-man pages.
bc9fd4
 .SH ADDITIONAL NOTES
bc9fd4
 Lock recovery after a reboot is critical to maintaining data integrity
bc9fd4
 and preventing unnecessary application hangs.
bc9fd4
@@ -445,7 +423,6 @@ network transport capability database
bc9fd4
 .BR rpc.nfsd (8),
bc9fd4
 .BR rpcbind (8),
bc9fd4
 .BR tcpd (8),
bc9fd4
-.BR hosts_access (5),
bc9fd4
 .BR iptables (8),
bc9fd4
 .BR netconfig (5)
bc9fd4
 .sp