RPC_GSS_SECCREATE(3) BSD Library Functions Manual RPC_GSS_SECCREATE(3)NAMErpc_gss_seccreate — create a security context using the RPCSEC_GSS proto‐
rpc_gss_seccreate(CLIENT *clnt, const char *principal,
const char *mechanism, rpc_gss_service_t service, const char *qop,
This function is used to establish a security context between an applica‐
tion and a remote peer using the RPSEC_GSS protocol.
clnt An RPC handle which is connected to the remote peer
principal The name of the service principal on the remote peer. For
instance, a principal such as "firstname.lastname@example.org"
might be used by an application which needs to contact an
mechanism The desired mechanism for this security context. The value
of mechanism should be the name of one of the security
mechanisms listed in /etc/gss/mech.
service Type of service requested.
The default - typically the same as
RPC headers only are integrity protected by a
RPC headers and data are integrity protected
by a checksum.
RPC headers are integrity protected by a
checksum and data is encrypted.
qop Desired quality of protection or NULL for the default.
Available values are lised in /etc/gss/qop
options_req Extra security context options to be passed to the underly‐
ing GSS-API mechanism. Pass NULL to supply default values.
options_ret Various values returned by the underlying GSS-API mecha‐
nism. Pass NULL if these values are not required.
If the security context was created successfully, a pointer to an AUTH
structure that represents the context is returned. To use this security
context for subsequent RPC calls, set clnt->cl_auth to this value.
SEE ALSOrpc(3), gssapi(3), mech(5), qop(5), rpcset_gss(3)HISTORY
The rpc_gss_seccreate function first appeared in FreeBSD 8.0.
This manual page was written by Doug Rabson ⟨dfr@FreeBSD.org⟩.
BSD January 26, 2010 BSD