Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gss_get_mic(3) [hpux man page]

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)

Check Out this Related Man Page

gss_wrap_size_limit(3)					     Library Functions Manual					    gss_wrap_size_limit(3)

NAME
gss_wrap_size_limit() - determine a token-size limit for gss_wrap on a context SYNOPSIS
DESCRIPTION
The routine allows an application to determine the maximum message size that, if presented to 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 applica- tion to fragment messages prior to applying protection. Input Parameters context_handle Specifies the context on which the message is sent. conf_req_flag Specifies the requested level of confidentiality and integrity services, as follows: Non-zero Both confidentiality and integrity services are requested. Zero Only integrity services are requested. qop_req Specifies the cryptographic algorithm, or quality of protection. A mechanism-specific default may be requested by setting qop_req to req_output_size The desired maximum size for tokens emitted by Output Parameters max_input_size The maximum input message size that may be presented to in order to guarantee that the emitted token shall be no larger than req_output_size bytes. 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 identified in the context_handle parameter was not valid. The context has already expired. The specified QOP is not supported by the mechanism. AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
gss_wrap(3). The manpages for DCE-GSSAPI are included with the DCE-CoreTools product. To see those manpages add to gss_wrap_size_limit(3)
Man Page