大网数据广告活动
账户与安全

Protecting Messages Using Microsoft Digest

· 52CE 我爱测

Explains how to protect messages using Microsoft Digest.

HTTP and SASL

As a means of detecting certain types of security violations, the client and server use the security support provider interface (SSPI) message integrity functions MakeSignature and VerifySignature to protect messages.

A client calls the MakeSignature function to sign a message using its security context. The server uses the VerifySignature function to verify the message's origin. In addition to verifying the signature that accompanies the message, the VerifySignature function also checks that the nonce count (specified by the nc directive) is one greater than the last count sent for the nonce. If this is not the case, the VerifySignature function returns an SEC_OUT_OF_SEQUENCE error code.

SASL Only

The EncryptMessage (General) and DecryptMessage (General) functions supply confidentiality for post-authentication messages exchanged between client and server.

In order to use the message confidentiality functions, the server and client must have established a security context with the following attributes:

  • Quality of protection, specified by the qop directive, must be "auth-conf".
  • An encryption mechanism must have been specified by means of the cipher directive.

Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Win32 documentation
适用范围
Windows Win32 API · Source date 05/31/2018
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。