gss_process_context_token(3) [hpux man page]

gss_process_context_token(3)				     Library Functions Manual				      gss_process_context_token(3)

NAME

       gss_process_context_token() - process a context to the security service

SYNOPSIS


DESCRIPTION

       The routine passes tokens generated by the 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 or routine.  If the tokens are associated with  the  per-message	security  service,
       they are passed to the or routine.

       Tokens generated by the routine are passed by the routine to the security service for processing.

   Input Parameters
       context_handle	     Specifies the context handle on which the security service processes the token.

       input_token_buffer    Specifies an opaque pointer to the first byte of the token to be processed.

   Output Parameters
       minor_status	     Returns a status code from the security mechanism.

STATUS CODES

       The following status codes can be returned:

       The routine was completed successfully.

       Consistency checks performed on the
				input_token parameter failed.

       The routine failed. See the
				minor_status parameter return value for more information.

       The supplied context handle did not refer to a valid context.

AUTHOR

       was developed by Sun Microsystems, Inc.

SEE ALSO

       gss_accept_sec_context(3), gss_delete_sec_context(3), gss_init_sec_context(3), gss_verify_mic(3), gss_unseal(3).

       The manpages for DCE-GSSAPI are included with the DCE-CoreTools product.  To see those manpages add to

														      gss_process_context_token(3)

gss_get_mic(3)						     Library Functions Manual						    gss_get_mic(3)

NAME

       gss_get_mic() - calculate a cryptographic message integrity code (MIC) for a message and return in a token

SYNOPSIS

       DESCRIPTION
	      The routine generates a cryptographic message integrity code (MIC) for the supplied message and places the MIC in a token for trans-
	      fer to the peer application.  The qop_req parameter allows a choice between several cryptographic algorithms, if	supported  by  the
	      chosen mechanism.

   Input Parameters
       context_handle	     Specifies the context on which the message is sent.

       qop_req		     Specifies the cryptographic algorithm, or quality of protection.  To accept the default quality of protection offered
			     by the chosen mechanism specify

       message_buffer	     Specifies the message to be protected.

   Output Parameters
       msg_token	     Buffer to receive the sealed message.

       minor_status	     Returns a status code from the security mechanism.

STATUS CODES

       The following status codes can be returned:

       The routine was completed successfully.

       The context has already expired.

       The context is recognized but the associated
				credentials have expired.

       The context identified in the
				context_handle parameter was not valid.

       The specified QOP is not supported by the mechanism.

AUTHOR

       was developed by Sun Microsystems, Inc.

SEE ALSO

       gss_verify_mic(3).

       The manpages for DCE-GSSAPI are included with the DCE-CoreTools product.  To see those manpages add to

																    gss_get_mic(3)