Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The RRASM data and RRASM operations specified by this implementation are to be protected by access checks based on the identity of the RPC client.
Servers implementing this specification are not to allow anonymous RPC connections and are to protect RRAS access to all data and operations with access control checks based on client identity.
RPC over named pipes is not to be used by clients or servers implementing this specification because it is vulnerable to man-in-the-middle attacks. They are to use RPC over TCP/IP instead.
Using RPC_C_AUTHN_LEVEL_PKT_PRIVACY as the RPC authentication level provides data confidentiality for the communication between client and server. The server implementing this protocol is to support clients requesting RPC_C_AUTHN_LEVEL_PKT_PRIVACY. The server can enforce this in order to protect the privacy of the communication between the client and the server.