gss_wrap_size_limit(3) [hpux 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)
Check Out this Related Man Page
gss_wrap(3) Library Functions Manual gss_wrap(3) NAME
gss_wrap() - attach a message integrity code (MIC) to a message, and optionally encrypt the message content SYNOPSIS
DESCRIPTION
The 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 rou- tine returns a status of 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 input_message_buffer Specifies the message to be protected. Output Parameters conf_state Returns the requested level of confidentiality and integrity services, as follows: Non-zero Confidentiality, data origin, authentication, and integrity services have been applied. Zero Only integrity and data origin services have been applied. output_message_buffer Returns the buffer to receive the protected 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 routine failed. Check the minor_status parameter for details. 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_unwrap(3), gss_wrap_size_limit(3). The manpages for DCE-GSSAPI are included with the DCE-CoreTools product. To see those manpages add to gss_wrap(3)