|Skip Navigation Links|
|Exit Print View|
|man pages section 3: Networking Library Functions Oracle Solaris 10 1/13 Information Library|
- verify integrity of a received message
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);
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.
The parameter descriptions for gss_verify_mic() follow:
The status code returned by the underlying mechanism.
Identifies the context on which the message arrived.
The message to be verified.
The token associated with the message.
Specifies the quality of protection gained from the MIC. Specify NULL if this parameter is not required.
gss_verify_mic() may return the following status codes:
The token failed consistency checks.
The MIC was incorrect.
The token was valid and contained a correct MIC for the message, but it had already been processed.
The token was valid and contained a correct MIC for the message, but it is too old to check for duplication.
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.
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.
The context has already expired.
The context_handle parameter did not identify a valid context.
The underlying mechanism detected an error for which no specific GSS status code is defined. The mechanism-specific status code reported by means of the minor_status parameter details the error condition.
See attributes(5) for descriptions of the following attributes: