rpc_gss_seccreate(3N) rpc_gss_seccreate(3N)
NAME
rpc_gss_seccreate() - create a security context using the RPCSEC_GSS protocol
SYNOPSIS
DESCRIPTION
is used by an application to create a security context using the protocol, making use of the underlying network layer. allows an applica-
tion to specify the type of security mechanism (for example, Kerberos v5), the type of service (for example, integrity checking) and the
Quality of Protection (QOP) desired for transferring data.
PARAMETERS
Information on data types for parameters may be found on the rpcsec_gss(3N) manpage.
clnt This is the RPC client handle. clnt may be obtained, for example, from
principal This is the identity of the server principal, specified in the form service@host, where service is the name of the service
the client wishes to access and host is the fully qualified name of the host where the service resides (for example,
mechanism This is an ASCII string which indicates which security mechanism to use with this data. Appropriate mechanisms may be found
in the file Additionally, returns a list of supported security mechanisms as NULL-terminated strings.
service_type This sets the initial type of service for the session: privacy, integrity, authentication, or none.
qop This is an ASCII string which sets the quality of protection (QOP) for the session. Appropriate values for this string may
be found in the file Additionally, supported QOPs are returned as NULL-terminated strings by
options_req This structure contains options which are passed directly to the underlying layer. If the caller specifies NULL for this
parameter, defaults are used.
options_ret These options are returned to the caller. If the caller does not need to see these options, then it may specify NULL for
this parameter.
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 and before These functions should not be
called by a multithreaded application that supports asynchronous cancellation or asynchronous signals.
RETURN VALUE
returns a security context handle (an RPC authentication handle) of type If cannot return successfully, the application can get an error
number by calling
WARNINGS
Contexts may be destroyed normally, with See the auth_destroy(3N) manpage.
FILES
File containing valid security mechanisms.
File containing valid QOP values.
SEE ALSO
auth_destroy(3N), rpc(3N), rpc_gss_get_error(3N), rpc_gss_get_mechanisms(3N), rpcsec_gss(3N), mech(4), qop(4).
rpc_gss_seccreate(3N)
