rpc_gss_mech_to_oid.3n (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

rpc_gss_mech_to_oid(3N) rpc_gss_mech_to_oid(3N)

NAME

rpc_gss_mech_to_oid(), rpc_gss_qop_to_num() - map mechanism, QOP strings to non-string values

SYNOPSIS

#include <rpc/rpcsec_gss.h>

bool_t rpc_gss_mech_to_oid(

char *mech,

rpc_gss_OID *oid);

bool_t rpc_gss_qop_to_num(

char *qop,

char *mech,

u_int *num);

DESCRIPTION

Because in-kernel RPC routines use non-string values for mechanism and Quality of Protection (QOP),

these routines exist to map strings for these attributes to their non-string counterparts. (The non-string

values for QOP and mechanism are also found in the

/etc/gss/qop and /etc/gss/mech

ﬁles,

respectively.)

rpc_gss_mech_to_oid()

takes a string representing a mechanism, as well as a

pointer to a

rpc_gss_OID object identiﬁer structure. It then gives this structure values corresponding

to the indicated mechanism, so that the application can now use the OID directly with RPC routines.

rpc_gss_qop_to_num()

does much the same thing, taking strings for QOP and mechanism and

returning a number.

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 be found in

the

/etc/gss/mech ﬁle.

oid An object identiﬁer of type

rpc_gss_OID, whose elements are usable by kernel-level RPC

routines.

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 ﬁle

/etc/gss/qop.

num The non-string value for the QOP.

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

Both functions return

TRUE if they are successful, FALSE otherwise.

FILES

/etc/gss/mech File containing valid security mechanisms.

/etc/gss/qop File containing valid QOP values.