GSS_S_BAD_SIG     The signature was incorrect

      GSS_S_DUPLICATE_TOKEN The token was valid, and contained a correct
                        signature for the message, but it had already
                        been processed

      GSS_S_OLD_TOKEN   The token was valid, and contained a correct
                        signature for the message, but it is too old

      GSS_S_UNSEQ_TOKEN The token was valid, and contained a correct
                        signature for the message, but has been
                        verified out of sequence; an earlier token has
                        been signed or sealed by the remote
                        application, but not yet been processed
                        locally.

      GSS_S_CONTEXT_EXPIRED The context has already expired

      GSS_S_CREDENTIALS_EXPIRED The context is recognized, but
                        associated credentials have expired






 
RFC 1509            GSSAPI - Overview and C bindings      September 1993


      GSS_S_NO_CONTEXT  The context_handle parameter did not identify a
                        valid context

      GSS_S_FAILURE     Failure.  See minor_status for more information.

3.10. gss_seal

      OM_uint32  gss_seal (
                     OM_uint32 *     minor_status,
                     gss_ctx_id_t    context_handle,
                     int             conf_req_flag,
                     int             qop_req
                     gss_buffer_t    input_message_buffer,
                     int *           conf_state,
                     gss_buffer_t    output_message_buffer)

   Purpose:

   Cryptographically signs and optionally encrypts the specified
   input_message.  The output_message contains both the signature and
   the message.  The qop_req parameter allows a choice between several
   cryptographic algorithms, if supported by the chosen mechanism.

   Parameters:

      minor_status      integer, modify
                        Mechanism specific status code.

      context_handle    gss_ctx_id_t, read
                        identifies the context on which the message
                        will be sent

      conf_req_flag     boolean, read
                        True - Both confidentiality and integrity
                               services are requested
                        False - Only integrity service is requested

      qop_req           integer, read, optional
                        Specifies required quality of protection.  A
                        mechanism-specific default may be requested by
                        setting qop_req to GSS_C_QOP_DEFAULT.  If an
                        unsupported protection strength is requested,
                        gss_seal will return a major_status of
                        GSS_S_FAILURE.

      input_message_buffer   buffer, opaque, read
                             message to be sealed





 
RFC 1509            GSSAPI - Overview and C bindings      September 1993


      conf_state        boolean, modify
                        True - Confidentiality, data origin
                               authentication and integrity services
                               have been applied
                        False - Integrity and data origin services only
                                has been applied.

      output_message_buffer  buffer, opaque, modify
                             buffer to receive sealed message

   Function value:

      GSS status code: