gss_wrap_size_limit(3)gss_wrap_size_limit(3)NAMEgss_wrap_size_limit() - determine a token-size limit for gss_wrap on a
The routine allows an application to determine the maximum message size
that, if presented to with the same conf_req_flag and qop_req parame‐
ters, will result in an output token containing no more than the
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.
context_handle Specifies the context on which the message is
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
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
max_input_size The maximum input message size that may be pre‐
sented to in order to guarantee that the emitted
token shall be no larger than req_output_size
minor_status Returns a status code from the security mecha‐
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.
was developed by Sun Microsystems, Inc.
The manpages for DCE-GSSAPI are included with the DCE-CoreTools prod‐
uct. To see those manpages add to