NAME
rpc_gss_set_svc_name() — send a principal name to a server
SYNOPSIS
#include <rpc/rpcsec_gss.h>
bool_t rpc_gss_set_svc_name(
char *principal,
char *mechanism,
u_int req_time,
u_int program,
u_int version);
DESCRIPTION
rpc_gss_set_svc_name()
sets the name of a principal the server is to represent.
If a server is going to act as more than one principal,
this procedure can be invoked for every such principal.
PARAMETERS
Information on
RPCSEC_GSS
data types for parameters may be found on the
rpcsec_gss(3N)
manpage.
- principal
An ASCII string representing the server's principal name,
given in the form of
service@host.
- mech
An ASCII string representing the security mechanism in use.
Valid strings may be found in the
/etc/gss/mech
file, or by using
rpc_gss_get_mechanisms().
- req_time
The time, in seconds, for which a credential should be valid.
Note that the
req_time
is a hint to the underlying mechanism.
The actual time that the credential will remain valid is
mechanism dependent.
In the case of kerberos the actual time will be
GSS_C_INDEFINITE.
- program
The RPC program number for this service.
- version
The RPC version number for this service.
MULTITHREAD USAGE
- Thread Safe:
Yes
- Cancel Safe:
Yes
- Fork Safe:
No
- Async-cancel Safe:
No
- Async-signal Safe:
No
These functions can be called safely in a multithreaded environment.
They may be cancellation points in that they call functions that are
cancel points.
In a multithreaded environment, these functions are
not safe to be called by a child process after
fork()
and before
exec().
These functions should not be called by a multithreaded application
that supports asynchronous cancellation or asynchronous signals.
RETURN VALUE
rpc_gss_set_svc_name()
returns
TRUE
if it is successful; otherwise, use
rpc_gss_get_error()
to get the error associated with the failure.
FILES
- /etc/gss/mech
File containing valid security mechanisms
Printable version
