Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gss_verify_mic(3gss) [sunos man page]

gss_verify_mic(3GSS)				  Generic Security Services API Library Functions			      gss_verify_mic(3GSS)

NAME
gss_verify_mic - verify integrity of a received message SYNOPSIS
cc -flag ... file ...-lgss [library ...] #include <gssapi/gssapi.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); DESCRIPTION
The gss_verify_mic() function 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(3GSS) to provide secure framing, the GSS-API supports the calculation and verification of MICs over zero-length messages. PARAMETERS
The parameter descriptions for gss_verify_mic() follow: minor_status The status code returned by the underlying mechanism. context_handle Identifies the context on which the message arrived. message_buffer The message to be verified. token_buffer The token associated with the message. qop_state Specifies the quality of protection gained from the MIC. Specify NULL if this parameter is not required. ERRORS
gss_verify_mic() may return the following status codes: 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 duplica- tion. GSS_S_UNSEQ_TOKEN The token was valid and contained a correct MIC for the message, but it 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 it 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. GSS_S_FAILURE The underlying mechanism detected an error for which no specific GSS status code is defined. The mecha- nism-specific status code reported by means of the minor_status parameter details the error condition. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWgss (32-bit) | +-----------------------------+-----------------------------+ | |SUNWgssx (64-bit) | +-----------------------------+-----------------------------+ |MT-Level |Safe | +-----------------------------+-----------------------------+ SEE ALSO
gss_wrap(3GSS), attributes(5) Solaris Security for Developers Guide SunOS 5.10 15 Jan 2003 gss_verify_mic(3GSS)

Check Out this Related Man Page

gss_verify_mic(3)							gss							 gss_verify_mic(3)

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 sup- port 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 soft- ware: http://www.gnu.org/gethelp/ COPYRIGHT
Copyright (C) 2003-2011 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. gss 1.0.2 gss_verify_mic(3)
Man Page