mirror of
https://git.FreeBSD.org/src.git
synced 2024-12-25 11:37:56 +00:00
a9148abd9d
and server. This replaces the RPC implementation of the NFS client and server with the newer RPC implementation originally developed (actually ported from the userland sunrpc code) to support the NFS Lock Manager. I have tested this code extensively and I believe it is stable and that performance is at least equal to the legacy RPC implementation. The NFS code currently contains support for both the new RPC implementation and the older legacy implementation inherited from the original NFS codebase. The default is to use the new implementation - add the NFS_LEGACYRPC option to fall back to the old code. When I merge this support back to RELENG_7, I will probably change this so that users have to 'opt in' to get the new code. To use RPCSEC_GSS on either client or server, you must build a kernel which includes the KGSSAPI option and the crypto device. On the userland side, you must build at least a new libc, mountd, mount_nfs and gssd. You must install new versions of /etc/rc.d/gssd and /etc/rc.d/nfsd and add 'gssd_enable=YES' to /etc/rc.conf. As long as gssd is running, you should be able to mount an NFS filesystem from a server that requires RPCSEC_GSS authentication. The mount itself can happen without any kerberos credentials but all access to the filesystem will be denied unless the accessing user has a valid ticket file in the standard place (/tmp/krb5cc_<uid>). There is currently no support for situations where the ticket file is in a different place, such as when the user logged in via SSH and has delegated credentials from that login. This restriction is also present in Solaris and Linux. In theory, we could improve this in future, possibly using Brooks Davis' implementation of variant symlinks. Supporting RPCSEC_GSS on a server is nearly as simple. You must create service creds for the server in the form 'nfs/<fqdn>@<REALM>' and install them in /etc/krb5.keytab. The standard heimdal utility ktutil makes this fairly easy. After the service creds have been created, you can add a '-sec=krb5' option to /etc/exports and restart both mountd and nfsd. The only other difference an administrator should notice is that nfsd doesn't fork to create service threads any more. In normal operation, there will be two nfsd processes, one in userland waiting for TCP connections and one in the kernel handling requests. The latter process will create as many kthreads as required - these should be visible via 'top -H'. The code has some support for varying the number of service threads according to load but initially at least, nfsd uses a fixed number of threads according to the value supplied to its '-n' option. Sponsored by: Isilon Systems MFC after: 1 month |
||
|---|---|---|
| .. | ||
| Makefile | ||
| rpc_gss_get_error.3 | ||
| rpc_gss_get_mech_info.3 | ||
| rpc_gss_get_mechanisms.3 | ||
| rpc_gss_get_principal_name.3 | ||
| rpc_gss_get_versions.3 | ||
| rpc_gss_getcred.3 | ||
| rpc_gss_is_installed.3 | ||
| rpc_gss_max_data_length.3 | ||
| rpc_gss_mech_to_oid.3 | ||
| rpc_gss_oid_to_mech.3 | ||
| rpc_gss_qop_to_num.3 | ||
| rpc_gss_seccreate.3 | ||
| rpc_gss_set_callback.3 | ||
| rpc_gss_set_defaults.3 | ||
| rpc_gss_set_svc_name.3 | ||
| rpc_gss_svc_max_data_length.3 | ||
| rpcsec_gss_conf.c | ||
| rpcsec_gss_int.h | ||
| rpcsec_gss_misc.c | ||
| rpcsec_gss_prot.c | ||
| rpcsec_gss.3 | ||
| rpcsec_gss.c | ||
| svc_rpcsec_gss.c | ||
| Symbol.map | ||