NAME

gss_verify — Checks that the cryptographic signature fits the supplied message

Synopsis

OM_uint32  gss_verify(
OM_uint32 ∗minor_status,
gss_ctx_id_t context_handle,
gss_buffer_t message_buffer,
gss_buffer_t token_buffer,
int qop_state);

Parameters

Input

context_handle
Specifies the context on which the message arrived.

message_buffer
Specifies the message to be verified.

token_buffer
Specifies the signature token to be associated with the message.

Output

qop_stateReturns the cryptographic algorithm, or quality of protection, from the signature. 

minor_status
Returns a status code from the security mechanism.

Description

The gss_verify() routine checks that an encrypted signature, in the token_buffer parameter, fits the message in the message_buffer buffer.  The application receiving the message can use the qop_state parameter to check the message’s protection. 

Errors

The following describes a partial list of errors that might be returned.  Refer to the OSF DCE Problem Determination Guide for complete descriptions of all error messages. 

GSS_S_COMPLETE
The routine was completed successfully.

GSS_S_CONTEXT_EXPIRED
The context has already expired.

GSS_S_CREDENTIALS_EXPIRED
The context is recognized but the associated credentials have expired.

GSS_S_FAILURE
The routine failed.   Check the minor_status parameter for details. 

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

Related Information

Functions: gss_seal(3sec), gss_sign(3sec).