rpc_gss_mech_to_oid(), rpc_gss_qop_to_num() — map mechanism, QOP strings to non-string values
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
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
does much the same thing, taking strings for QOP and mechanism and
returning a number.
data types for parameters may be found on the
An ASCII string representing the security mechanism in use.
Valid strings may be found in the
An object identifier of type
whose elements are usable by kernel-level RPC routines.
This is an ASCII string which sets the quality of protection (QOP) for
Appropriate values for this string may be found in the file
The non-string value for the QOP.
- Thread Safe:
- Cancel Safe:
- Fork Safe:
- Async-cancel Safe:
- Async-signal Safe:
These functions can be called safely in a multithreaded environment.
They may be cancellation points in that they call functions that are
In a multithreaded environment, these functions are
not safe to be called by a child process after
These functions should not be called by a multithreaded application
that supports asynchronous cancellation or asynchronous signals.
Both functions return
if they are successful,
File containing valid security mechanisms.
File containing valid QOP values.