4 .\" Copyright (C) 2003 J. Bruce Fields <bfields@umich.edu>
5 .TH rpc.gssd 8 "14 Mar 2007"
7 rpc.gssd \- rpcsec_gss daemon
9 .B "rpc.gssd [-f] [-n] [-k keytab] [-p pipefsdir] [-v] [-r] [-d ccachedir]"
11 The rpcsec_gss protocol gives a means of using the gss-api generic security
12 api to provide security for protocols using rpc (in particular, nfs). Before
13 exchanging any rpc requests using rpcsec_gss, the rpc client must first
14 establish a security context. The linux kernel's implementation of rpcsec_gss
15 depends on the userspace daemon
17 to establish security contexts. The
19 daemon uses files in the rpc_pipefs filesystem to communicate with the kernel.
26 in the foreground and sends output to stderr (as opposed to syslogd)
31 treats accesses by the user with UID 0 specially, and uses
32 "machine credentials" for all accesses by that user which
33 require Kerberos authentication.
34 With the \-n option, "machine credentials" will not be used
35 for accesses by UID 0. Instead, credentials must be obtained
36 manually like all other users. Use of this option means that
37 "root" must manually obtain Kerberos credentials before
38 attemtpting to mount an nfs filesystem requiring Kerberos
44 to use the keys for principals nfs/hostname in
46 to obtain machine credentials.
47 The default value is "/etc/krb5.keytab".
52 where to look for the rpc_pipefs filesystem. The default value is
53 "/var/lib/nfs/rpc_pipefs".
58 where to look for kerberos credential files. The default value is "/tmp".
61 Increases the verbosity of the output (can be specified multiple times).
64 If the rpcsec_gss library supports setting debug level,
65 increases the verbosity of the output (can be specified multiple times).
70 Dug Song <dugsong@umich.edu>
72 Andy Adamson <andros@umich.edu>
74 Marius Aamodt Eriksen <marius@umich.edu>
76 J. Bruce Fields <bfields@umich.edu>