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

RpcServerRegisterAuthInfo doesn't deny unauthorized users

· 52CE 我爱测

When security providers are registered on the server with the RpcServerRegisterAuthInfo function, an authentication option is added; not an authentication requirement.

When security providers are registered on the server with the RpcServerRegisterAuthInfo function, an authentication option is added; not an authentication requirement. That means that previous registrations with RpcServerRegisterAuthInfo aren't replaced. It also means that an unauthenticated client that could connect before can still connect.

Just calling the RpcServerRegisterAuthInfo function doesn't disallow unauthenticated clients from connecting. If they could connect before, then they can still connect; but function calls such as RpcImpersonateClient and RpcGetAuthorizationContextForClient will fail. So when the RpcServerRegisterAuthInfo function is called, potential attackers have not been weeded out—rather, authorized clients are given a chance to prove their identity. So you must still put in place checks to determine whether potential attackers are attempting to connect.

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 02/21/2023
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

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

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