大网数据广告活动
网络与域名解析

Which Security Provider to Use

· 52CE 我爱测

All other things being equal, use RPC_C_AUTHN_GSS_KERBEROS or RPC_C_AUTHN_GSS_NEGOTIATE.

All other things being equal, use RPC_C_AUTHN_GSS_KERBEROS or RPC_C_AUTHN_GSS_NEGOTIATE. Each provides the most scalable and secure service. If you use RPC_C_AUTHN_GSS_NEGOTIATE on the server, this allows down-level clients, such as NTLM clients, to connect to your server. If that is undesirable, either limit the choice to RPC_C_AUTHN_GSS_KERBEROS only, or call RpcBindingInqAuthClientEx to determine which security provider the client is using, and deny access to clients using NTLM. The preferred method of establishing which security provider the client is using is the RpcServerInqCallAttributes function.

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)

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

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