diff options
author | rwatson <rwatson@FreeBSD.org> | 2001-04-05 06:12:38 +0000 |
---|---|---|
committer | rwatson <rwatson@FreeBSD.org> | 2001-04-05 06:12:38 +0000 |
commit | c124492b003963cbe9d4ff503bb063aa0de0244c (patch) | |
tree | 428c8e0549e62aa4bd26c9722ac5eedd276cb7da /sys/nfsclient/krpc.h | |
parent | cd9ec299e38483f5740e11e6b30f03f0c20fbb2b (diff) | |
download | FreeBSD-src-c124492b003963cbe9d4ff503bb063aa0de0244c.zip FreeBSD-src-c124492b003963cbe9d4ff503bb063aa0de0244c.tar.gz |
o Rather than arbitrarily construct a credential in the nfs_statfs()
VFS operation, make use of the calling process's credential. This
solution may not be ideal (there are a number of other possible
proposals, including making use of the proc0 credential, adding a
credential argument to the VFSOP, and switching from a hard-coded
ucred to a hard-coded nfscred), it is simple and appears to
work. The arguments against using simply crget() are fairly
strong: it is the only place in the code (other than a nearly
identical invocation in ncp) where crget() is invoked, other than
in the process credential creation code; as ucred becomes extensible,
this use of crget() without appropriate context results in less and
less meaningful credential data. The implementation here will
probably be tweaked as a result of experimentation and further
exploration of the requirements. In the mean-time, it allows
progress to be made in ucred expansion for new security models without
causing a crash every time df is used on an NFS mounted file system.
This code has been interop tested against FreeBSD and Solaris NFS
servers. While using the process credentials should not introduce
interop problems, please let me know if any turn out to exist.
Reviewed by: freebsd-arch
Diffstat (limited to 'sys/nfsclient/krpc.h')
0 files changed, 0 insertions, 0 deletions