rpc_gss_get_mechanisms.3n (2010 09)

r
rpc_gss_get_mechanisms(3N) rpc_gss_get_mechanisms(3N)
NAME
rpc_gss_get_mechanisms(), rpc_gss_get_mech_info(), rpc_gss_get_versions(), rpc_gss_is_installed() - get
information on mechanisms and RPC version
SYNOPSIS
#include <rpc/rpcsec_gss.h>
char **rpc_gss_get_mechanisms();
char **rpc_gss_get_mech_info(
char *mech,
rpc_gss_service_t *
service );
bool_t rpc_gss_get_versions(
u_int *vers_hi ,
u_int *vers_lo );
bool_t rpc_gss_is_installed(
char *mech);
DESCRIPTION
These "convenience functions" return information on available security mechanisms and versions of
RPCSEC_GSS.
rpc_gss_get_mechanisms()
Returns a list of supported security mechanisms as a null-terminated list of character strings.
rpc_gss_get_mech_info()
Takes two arguments: an ASCII string representing a mechanism type (for example,
kerberosv5)
and a pointer to a
rpc_gss_service_t enum
. rpc_gss_get_mech_info() will return
NULL upon error or if no
/etc/gss/qop file is present. Otherwise, it returns a null-terminated
list of character strings of supported Quality of Protections (QOPs) for this mechanism. NULL or
empty list implies only that the default QOP is available and can be specified to routines that need
to take a QOP string parameter as NULL or as an empty string.
rpc_gss_get_versions()
Returns the highest and lowest versions of RPCSEC_GSS supported.
rpc_gss_is_installed()
Takes an ASCII string representing a mechanism, and returns TRUE if the mechanism is installed.
PARAMETERS
Information on
RPCSEC_GSS data types for parameters may be found on the rpcsec_gss (3N) manpage.
mech An ASCII string representing the security mechanism in use. Valid strings may also be found
in the
/etc/gss/mech file.
service A pointer to a
rpc_gss_service_t enum, representing the current security service
(privacy, integrity, or none).
vers_hi , vers_lo
The highest and lowest versions of
RPCSEC_GSS supported.
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.
HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1