rpc_gss_get_mechanisms(3n) [hpux man page]

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


DESCRIPTION

       These "convenience functions" return information on available security mechanisms and versions of

       Returns a list of supported security mechanisms as a null-terminated
	      list of character strings.

       Takes two arguments: an ASCII string representing a mechanism type
	      (for example, and a pointer to a will return NULL upon error or if no 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.

       Returns the highest and lowest versions of
	      supported.

       Takes an ASCII string representing a mechanism, and returns
	      if the mechanism is installed.

PARAMETERS

       Information on 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 file.

       service	 A pointer to a representing the current security service (privacy, integrity, or none).

       vers_hi, vers_lo
		 The highest and lowest versions of 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 and before These functions should not be
       called by a multithreaded application that supports asynchronous cancellation or asynchronous signals.

BUGS

       The service argument for is currently irrelevant.

FILES

       File containing valid security mechanisms.

       File containing valid QOP values.

SEE ALSO

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

															rpc_gss_get_mechanisms(3N)

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


DESCRIPTION

       These "convenience functions" return information on available security mechanisms and versions of

       Returns a list of supported security mechanisms as a null-terminated
	      list of character strings.

       Takes two arguments: an ASCII string representing a mechanism type
	      (for example, and a pointer to a will return NULL upon error or if no 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.

       Returns the highest and lowest versions of
	      supported.

       Takes an ASCII string representing a mechanism, and returns
	      if the mechanism is installed.

PARAMETERS

       Information on 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 file.

       service	 A pointer to a representing the current security service (privacy, integrity, or none).

       vers_hi, vers_lo
		 The highest and lowest versions of 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 and before These functions should not be
       called by a multithreaded application that supports asynchronous cancellation or asynchronous signals.

BUGS

       The service argument for is currently irrelevant.

FILES

       File containing valid security mechanisms.

       File containing valid QOP values.

SEE ALSO

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

															rpc_gss_get_mechanisms(3N)