rpc_gss_mech_to_oid(3N)rpc_gss_mech_to_oid(3N)NAMErpc_gss_mech_to_oid(), rpc_gss_qop_to_num() - map mechanism, QOP
strings to non-string values
SYNOPSISDESCRIPTION
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 and files, respec‐
tively.) takes a string representing a mechanism, as well as a pointer
to a 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. does much the same thing,
taking strings for QOP and mechanism and returning a number.
PARAMETERS
Information on data types for parameters may be found on the rpc‐
sec_gss(3N) manpage.
mech An ASCII string representing the security mechanism in use.
Valid strings may be found in the file.
oid An object identifier of type 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
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 and before These functions should not
be called by a multithreaded application that supports asynchronous
cancellation or asynchronous signals.
RETURN VALUE
Both functions return if they are successful, otherwise.
FILES
File containing valid security mechanisms.
File containing valid QOP values.
SEE ALSOrpc(3N), rpc_gss_get_error(3N), rpc_gss_get_mechanisms(3N), rpc‐
sec_gss(3N), mech(4), qop(4).
rpc_gss_mech_to_oid(3N)
