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

Null Sessions

· 52CE 我爱测

Sometimes a call arriving on the null session can appear like an authenticated call.

Sometimes a call arriving on the null session can appear like an authenticated call. Specifically, calling the RpcBindingInqAuthClient function returns the authentication level and security provider used for the call. This operation does not mean the call was not on a null session. The two issues are orthogonal. On Microsoft Windows 2000, a remote procedure call can attempt to impersonate a caller and check the permissions after impersonation. On Microsoft Windows XP, it is faster to call the RpcServerInqCallAttributes function and check for the NullSession flag.

Another relevant difference exists between Windows 2000 and Windows XP. If only the RPC_IF_ALLOW_SECURE_ONLY flag is specified, calls on the null session go through in Windows 2000. In Windows XP, with the general tightening of default security settings, when this flag is specified, calls on the null session are rejected with access denied. However, even with the RPC_IF_ALLOW_SECURE_ONLY flag, RPC does not guarantee the privilege level of the calling user. All RPC checks is that the user has valid credentials. It is possible that the calling user is using the guest account or other low privileged accounts. Make sure the server does not assume high privilege once RPC_IF_ALLOW_SECURE_ONLY is used.

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)

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

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