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

Interface Registration Flags (Rpcdce.h)

· 52CE 我爱测

The following constants are used in the Flags parameter of the RpcServerRegisterIf2 and RpcServerRegisterIfEx functions.

The following constants are used in the Flags parameter of the RpcServerRegisterIf2 and RpcServerRegisterIfEx functions.

Constant Description
0 Standard interface semantics.
RPC_IF_ALLOW_CALLBACKS_WITH_NO_AUTH When this interface flag is registered, the RPC runtime invokes the registered security callback for all calls, regardless of identity, protocol sequence, or authentication level of the client. Note: This flag is available starting with Windows XP with SP2 and Windows Server 2003 with SP1. When this flag is not set, RPC automatically filters all unauthenticated calls before they reach the security callback.
RPC_IF_ALLOW_LOCAL_ONLY When this interface flag is registered, the RPC runtime rejects calls made by remote clients. All local calls using ncadg_* and ncacn_* protocol sequences are also rejected, with the exception of ncacn_np. RPC allows ncacn_NP calls only if the call does not come from SRV. Calls from ncalrpc are always processed. Note: This flag is available starting with Windows XP with SP2 and Windows Server 2003 with SP1.
RPC_IF_AUTOLISTEN This is an auto-listen interface. The run time begins listening for calls as soon as the first autolisten interface is registered, and stops listening when the last autolisten interface is unregistered.
RPC_IF_OLE Reserved for OLE. Do not use this flag.
RPC_IF_ALLOW_UNKNOWN_AUTHORITY Currently not implemented.
RPC_IF_ALLOW_SECURE_ONLY Limits connections to clients that use an authorization level higher than RPC_C_AUTHN_LEVEL_NONE. Specifying this flag allows clients to come through on the NULL session. On Windows XP and Windows Server 2003, such clients are not allowed. Clients that fail the RPC_IF_ALLOW_SECURE_ONLY test receive an RPC_S_ACCESS_DENIED error. Using the RPC_IF_ALLOW_SECURE_ONLY flag does not imply or guarantee a high level of privilege on the part of the calling user. RPC only checks that the user has valid credentials; the calling user may be using the guest account or other low privileged accounts. Do not assume high privilege when RPC_IF_ALLOW_SECURE_ONLY is used.Windows NT 4.0 and Windows Me/98/95:
RPC_IF_SEC_NO_CACHE Disables security callback caching, forcing a security callback for each RPC call on a given interface. Note: This flag is available starting with Windows XP with SP2 and Windows Server 2003 with SP1.

Requirements

Requirement Value
Minimum supported client Windows 2000 Professional [desktop apps only]
Minimum supported server Windows 2000 Server [desktop apps only]
Header Rpcdce.h

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)

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

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