VerifySignature function
Applies to: desktop apps only
Verifies that a message signed by using the MakeSignature function was received in the correct sequence and has not been modified.
Syntax
SECURITY_STATUS SEC_Entry VerifySignature( __in PCtxtHandle phContext, __in PSecBufferDesc pMessage, __in ULONG MessageSeqNo, __out PULONG pfQOP );
Parameters
- phContext [in]
-
A handle to the security context to use for the message.
- pMessage [in]
-
Pointer to a SecBufferDesc structure that references a set of SecBuffer structures that contain the message and signature to verify. The signature is in a SecBuffer structure of type SECBUFFER_TOKEN.
- MessageSeqNo [in]
-
Specifies the 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 a ULONG variable that receives package-specific flags that indicate the quality of protection.
Some security packages ignore this parameter.
Return value
If the function verifies that the message was received in the correct sequence and has not been modified, the return value is SEC_E_OK.
If the function determines that the message is not correct according to the information in the signature, the return value can be one of the following error codes.
| Return code | Description |
|---|---|
|
The message was not received in the correct sequence. |
|
The message has been altered. |
|
The context handle specified by phContext is not valid. |
|
pMessage did not contain a valid SECBUFFER_TOKEN buffer, or contained too few buffers. |
|
The quality of protection negotiated between the client and server did not include integrity checking. |
Requirements
|
Minimum supported client | Windows 2000 Professional |
|---|---|
|
Minimum supported server | Windows 2000 Server |
|
Header |
|
|
Library |
|
|
DLL |
|
See also
Send comments about this topic to Microsoft
Build date: 3/13/2012
