Messages in this thread | | | Subject | Re: NFS inconsistent behaviour | From | Trond Myklebust <> | Date | Wed, 18 Oct 2006 14:37:12 -0400 |
| |
On Wed, 2006-10-18 at 13:57 -0400, Trond Myklebust wrote: > Note also that you _can_ change the range of ports used by the NFS > client itself at least. Just edit /proc/sys/sunrpc/{min,max}_resvport. > On the server side, you can use the 'insecure' option in order to allow > mounts that originate from non-privileged ports (i.e. port > 1024). > If you are using strong authentication (for instance RPCSEC_GSS/krb5) > then that actually makes a lot of sense, since the only reason for the > privileged port requirement was to disallow unprivileged NFS clients.
Oops... Something got lost there. That last sentence should read
...since the only reason for the privileged port requirement was to disallow unprivileged NFS clients that could be used to spoof other user identities via the weak AUTH_SYS authentication.
Cheers, Trond
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |