Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX Reference > R

rpc_gss_mech_to_oid(3N)

HP-UX 11i Version 3: February 2007
» 

Technical documentation

» Feedback
Content starts here

 » Table of Contents

 » Index

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 files, respectively.) rpc_gss_mech_to_oid() takes a string representing a mechanism, as well as a pointer to a rpc_gss_OID object identifier 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 file.

oid

An object identifier 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 file /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.

SEE ALSO

rpc(3N), rpc_gss_get_error(3N), rpc_gss_get_mechanisms(3N), rpcsec_gss(3N), mech(4), qop(4).

ONC+ Developer's Guide

Network Working Group RFC 2078

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1983-2007 Hewlett-Packard Development Company, L.P.