This section presents discussions of transport-level security, divided into the following topics:
When you use ncacn_np or ncalrpc as the protocol sequence, the server specifies a security descriptor for the endpoint at the time it selects the protocol sequence. For more information on protocol sequences, see Specifying Protocol Sequences. Your application provides the security descriptor as an additional parameter (an extension to the standard OSF-DCE parameters) on all functions that start with the prefixes RpcServerUseProtseq and RpcServerUseAllProtseqs. The security descriptor controls whether a client can connect to the endpoint.
Each process and thread is associated with a security token. This token includes a default security descriptor that is used for any objects that the process creates, such as the endpoint. If your application does not specify a security descriptor when calling a function with the prefixes RpcServerUseProtseq and RpcServerUseAllProtseqs, the RPC run-time library applies the default security descriptor from the process security token to the endpoint.
To guarantee that the server application is accessible to all clients, the administrator should start the server application on a process that has a default security descriptor that all clients can use. Generally, only system processes have a default security descriptor.
For more information about these functions and the functions RpcImpersonateClient and RpcRevertToSelf.
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.
