]> CyberLeo.Net >> Repos - FreeBSD/FreeBSD.git/commit
Fix the NFSv4 server to obey vfs.nfsd.nfs_privport.
authorRick Macklem <rmacklem@FreeBSD.org>
Thu, 20 Dec 2018 22:21:41 +0000 (22:21 +0000)
committerRick Macklem <rmacklem@FreeBSD.org>
Thu, 20 Dec 2018 22:21:41 +0000 (22:21 +0000)
commit23114c6c2af175a08730400a04f57991f301127f
tree7788a699b62bb690b04f192c22f796b4ff3bab0f
parent0c3bbec309a8ea169005002182c0765b4ca24d03
Fix the NFSv4 server to obey vfs.nfsd.nfs_privport.

When the NFSv4 server was coded, I believed that the specification authors
did not want NFSv4 servers to require a client to use a reserved port#.
However, recently it has been noted that the Linux NFSv4 server does support
a check for a reserved port#.
Since both the FreeBSD and Linux NFSv4 clients use a reserved port# by
default, enabling vfs.nfsd.nfs_privport to require a reserved port# for
NFSv4 the same as it does for NFSv2, 3 seems reasonable.
The only case where this could cause a POLA violation is a FreeBSD NFSv4
server with vfs.nfsd.nfs_privport set, but with NFSv4 clients doing mounts
without using a reserved port# (< 1024).

Tested by: chaz.newton58@gmail.com
PR: 234106
MFC after: 1 week
sys/fs/nfsserver/nfs_nfsdkrpc.c