4 .\" Copyright (C) 2003 J. Bruce Fields <bfields@umich.edu>
5 .TH rpc.gssd 8 "17 Mar 2003"
7 rpc.gssd \- rpcsec_gss daemon
9 .B "rpc.gssd [-f] [-k keytab] [-p pipefsdir] [-v]"
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 to use the keys for principals nfs/hostname in
33 to obtain machine credentials.
34 The default value is "/etc/krb5.keytab".
39 .\"looks for a cached ticket for user $UID in /tmp/krb5cc_$UID.
40 .\"With the -m option, the user with uid 0 will be treated specially, and will
41 .\"be mapped instead to the credentials for the principal nfs/hostname found in
43 .\"(This option is now the default and is ignored if specified.)
48 where to look for the rpc_pipefs filesystem. The default value is
49 "/var/lib/nfs/rpc_pipefs".
52 Increases the verbosity of the output (can be specified multiple times).
57 Dug Song <dugsong@umich.edu>
59 Andy Adamson <andros@umich.edu>
61 Marius Aamodt Eriksen <marius@umich.edu>
63 J. Bruce Fields <bfields@umich.edu>