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

  man pages->HP-UX 11i man pages -> gss_wrap_size_limit (3)              


 gss_wrap_size_limit(3)                               gss_wrap_size_limit(3)

 NAME    [Toc]    [Back]
      gss_wrap_size_limit() - determine a token-size limit for gss_wrap on a

 SYNOPSIS    [Toc]    [Back]
      #include <gssapi.h>

      OM_uint32  gss_wrap_size_limit (
                OM_uint32 *minor_status,
                const gss_ctx_id_t context_handle,
                int conf_req_flag,
                gss_qop_t qop_req,
                OM_uint32 req_output_size,
                OM_uint32 max_input_size)

 DESCRIPTION    [Toc]    [Back]
      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
      application to fragment messages prior to applying protection.

    Input Parameters    [Toc]    [Back]
      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

    Output Parameters    [Toc]    [Back]
      max_input_size        The maximum input message size that may be
                            presented to gss_wrap() in order to guarantee
                            that the emitted token shall be no larger than
                            req_output_size bytes.

 Hewlett-Packard Company            - 1 -   HP-UX 11i Version 2: August 2003

 gss_wrap_size_limit(3)                               gss_wrap_size_limit(3)

      minor_status          Returns a status code from the security

 STATUS CODES    [Toc]    [Back]
      The following status codes can be returned:

      GSS_S_COMPLETE           The routine was completed successfully.

      GSS_S_NO_CONTEXT         The context identified in the context_handle
                               parameter was not valid.

      GSS_S_CONTEXT_EXPIRED    The context has already expired.

      GSS_S_BAD_QOP            The specified QOP is not supported by the

 AUTHOR    [Toc]    [Back]
      gss_wrap_size_limit() was developed by Sun Microsystems, Inc.

 SEE ALSO    [Toc]    [Back]

      The manpages for DCE-GSSAPI are included with the DCE-CoreTools
      product.  To see those manpages add /opt/dce/share/man to MANPATH.

 Hewlett-Packard Company            - 2 -   HP-UX 11i Version 2: August 2003
[ Back ]
 Similar pages
Name OS Title
ulimit IRIX set or report file size limit
intr_strobe_ics_pct HP-UX limit for the percent of time a processor is allowed to spend in interrupt context
gss_wrap_size_limit Tru64 set the maximum input message size for the required maximum output token
strnlen Linux determine the length of a fixed-size string
wcsnlen Linux determine the length of a fixed-size wide-character string
gss_context_time Tru64 Determine remaining lifetime of security context.
wcswidth Linux determine columns needed for a fixed-size wide character string
gss_init_sec_context HP-UX establish a security context between the context initiator and a context acceptor
ulimit Tru64 Sets or reports a resource limit
ovbcopy Tru64 General: Copies a byte string with a specified limit
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service