Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This function verifies the signature of a message at the other end.

Syntax 

SECURITY_STATUS SEC_ENTRY VerifySignature( 
  PCtxtHandle
 phContext,
  PSecBufferDesc
 pMessage, 
  ULONG
 MessageSeqNo, 
  ULONG SEC_FAR*
 pfQOP 
);

Parameters

phContext

[in] Pointer to a CtxtHandlestructure identifying the context handle. For information on CtxtHandle, see SSPI Handles.

pMessage

[in] Pointer to a SecBufferDescstructure that references a set of SecBufferstructures containing the message and signature to verify. The signature is in a SecBufferstructure of type SECBUFFER_TOKEN.

MessageSeqNo

[in] The message sequence number expected by the transport application, if any. If the transport application does not maintain sequence numbers, this parameter is zero.

pfQOP

[out] Pointer to package-specific flags that indicate the quality of protection.

Return Value

This function returns SEC_E_OK to indicate that it verified that the message was received in the correct sequence and had not been modified. If the function determines that the message is not correct according to the information in the signature, it returns one of the error values described in the following table.

Value Description

SEC_E_OUT_OF_SEQUENCE

The message was not received in the correct sequence.

SEC_E_MESSAGE_ALTERED

The message has been altered.

Remarks

This function verifies that the message received was correct according to the information in the signature.

Requirements

Header security.h, sspi.h
Library secur32.lib
Windows Embedded CE Windows CE 2.10 and later
Windows Mobile Smartphone 2002 and later

See Also