Man Linux: Main Page and Category List

NAME

       gss_verify_mic - API function

SYNOPSIS

       #include <gss.h>

       OM_uint32  gss_verify_mic(OM_uint32  * minor_status, const gss_ctx_id_t
       context_handle, const gss_buffer_t message_buffer,  const  gss_buffer_t
       token_buffer, gss_qop_t * qop_state);

ARGUMENTS

       OM_uint32 * minor_status
                   (Integer, modify) Mechanism specific status code.

       const gss_ctx_id_t context_handle
                   (gss_ctx_id_t, read) Identifies the context on
                     which the message arrived.

       const gss_buffer_t message_buffer
                   (buffer, opaque, read) Message to be verified.

       const gss_buffer_t token_buffer
                   (buffer, opaque, read) Token associated with
                     message.

       gss_qop_t * qop_state
                   (gss_qop_t, modify, optional) Quality of protection
                     gained from MIC Specify NULL if not required.

DESCRIPTION

       Verifies  that  a  cryptographic MIC, contained in the token parameter,
       fits the supplied message.  The qop_state parameter  allows  a  message
       recipient  to  determine the strength of protection that was applied to
       the message.

       Since some application-level protocols may wish to use  tokens  emitted
       by gss_wrap() to provide "secure framing", implementations must support
       the calculation and verification of MICs over zero-length messages.

RETURN VALUE

       ‘GSS_S_COMPLETE‘: Successful completion.

       ‘GSS_S_DEFECTIVE_TOKEN‘: The token failed consistency checks.

       ‘GSS_S_BAD_SIG‘: The MIC was incorrect.

       ‘GSS_S_DUPLICATE_TOKEN‘: The token was valid, and contained  a  correct
       MIC for the message, but it had already been processed.

       ‘GSS_S_OLD_TOKEN‘: The token was valid, and contained a correct MIC for
       the message, but it is too old to check for duplication.

       ‘GSS_S_UNSEQ_TOKEN‘: The token was valid, and contained a  correct  MIC
       for  the  message, but has been verified out of sequence; a later token
       has already been received.

       ‘GSS_S_GAP_TOKEN‘: The token was valid, and contained a correct MIC for
       the message, but has been verified out of sequence; an earlier expected
       token has not yet been received.

       ‘GSS_S_CONTEXT_EXPIRED‘: The context has already expired.

       ‘GSS_S_NO_CONTEXT‘: The context_handle parameter  did  not  identify  a
       valid context.

REPORTING BUGS

       Report  bugs  to  <bug-gss@gnu.org>.  GNU Generic Security Service home
       page: http://www.gnu.org/software/gss/ General help using GNU software:
       http://www.gnu.org/gethelp/

COPYRIGHT

       Copyright © 2003-2010 Simon Josefsson.
       Copying  and  distribution  of this file, with or without modification,
       are permitted in any medium  without  royalty  provided  the  copyright
       notice and this notice are preserved.

SEE ALSO

       The  full  documentation for gss is maintained as a Texinfo manual.  If
       the info and gss programs are properly  installed  at  your  site,  the
       command

              info gss

       should give you access to the complete manual.