*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->HP-UX 11i man pages              
 gss_inquire_cred(3) -- provide the calling application information about a credential
    The gss_inquire_cred() routine provides information about a credential to the calling application. The calling application must first have called the gss_acquire_cred() routine for a handle for the credential.
 gss_inquire_cred_by_mech(3) -- provide the calling application permechanism information about a credential
    The gss_inquire_cred_by_mech() routine provides per-mechanism information about a credential.
 gss_inquire_mechs_for_name(3) -- list the mechanisms that support the
    The gss_inquire_mechs_for_name() routine returns the set of mechanisms supported by the GSS-API implementation that may be able to process the specified name.
 gss_inquire_names_for_mech(3) -- list the name-types supported by the specified mechanism
    The gss_inquire_names_for_mech() routine returns the set of nametypes supported by the specified mechanism.
 gss_process_context_token(3) -- process a context to the security service
    The gss_process_context_token() routine passes tokens generated by the gss_delete_security_context() routine to the security service. Usually, tokens are associated with either the context establishment or with per-message security services. If the tokens are associated with the context establishment, they are passed to the gss_init_sec_context() or gss_accept_sec_context() routine. If the tokens ...
 gss_release_buffer(3) -- free storage associated with a buffer
    The gss_release_buffer() routine deletes the buffer by freeing the storage associated with it.
 gss_release_cred(3) -- mark a credential for deletion
    The gss_release_cred() routine informs the GSSAPI that a credential is no longer required and marks it for deletion.
 gss_release_name(3) -- free storage associated with an internal name allocated by a GSSAPI routine
    The gss_release_name() routine deletes the internal name by freeing the storage associated with that internal name.
 gss_release_oid_set(3) -- free storage associated with a gss_OID_set object
    The gss_release_oid_set() routine frees storage that is associated with the gss_OID_set parameter and was allocated by a GSSAPI routine.
 gss_test_oid_set_member(3) -- check an OID set for a specified OID
    The gss_test_oid_set_member() routine checks an OID set to see if the specified OID is a member of the set. To add a member to an OID set, use the gss_add_oid_set_member() routine. The gss_test_oid_set_member() routine uses the value of the actual_mechs output parameter from the gss_acquire_cred() routine to get the list of OIDs. It checks this list to see if any of the OIDs are members of the OID...
 gss_unwrap(3) -- verify a message with attached message integrity code (MIC) and decrypt message content if necessary
    The gss_unwrap() routine converts a protected message to a usable form and verifies the embedded message integrity code (MIC). The conf_state parameter indicates whether the message was encrypted. The qop_state parameter indicates the quality of protection that was used to provide the confidentiality and integrity services.
 gss_verify_mic(3) -- check a cryptographic message integrity code (MIC) against a message to verify its integrity
    The gss_verify_mic() routine verifies that a cryptographic MIC, contained in the token_buffer parameter, fits the supplied message. The application receiving the message can use the qop_state parameter to check the strength of protection.
 gss_wrap(3) -- attach a message integrity code (MIC) to a message, and optionally encrypt the message content
    The gss_wrap() routine attaches a cryptographic message integrity code (MIC) and optionally encrypts the input_message. The output_message contains both the MIC and the message. Although the qop_req parameter enables a choice between several qualities of protection, if you specify an unsupported protection, the gss_wrap() routine returns a status of GSS_S_FAILURE.
 gss_wrap_size_limit(3) -- determine a token-size limit for gss_wrap on a context
    The gss_wrap_size_limit() routine allows an application to determine the maximum message size that, if presented to gss_wrap() with the same conf_req_flag and qop_req parameters, will result in an output token containing no more than the req_output_size bytes. This call is intended for use by applications that communicate over protocols that impose a maximum message size. It enables the applicatio...
 hosts_access(3) -- access control library
    The routines described here are a part of the libwrap.a library. They implement a rule-based access control language with optional shell commands that are executed when a rule fires. request_init() initializes a structure with information about a client request. request_set() updates an already initialized request structure. Both functions take a variable-length list of key-value pairs and return ...
<<  [Prev]  1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20  21  
22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  37  38  39  40  [Next]  >>
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service