Share via

3 Protocol Details

  • Article

This section specifies the behavior of the EFSRPC server in more detail. The client side of this protocol is simply a pass-through. There are no additional timers or other state requirements on the client side of this protocol. Calls made by the higher-layer protocol or application are passed directly to the transport, and the results returned by the transport are passed directly back to the higher-layer protocol or application. The client SHOULD<32> attempt to associate the use of suitable RPC security mechanisms with its binding when making the EfsRpcOpenFileRaw call, so that the data transfer is protected from man-in-the-middle attacks.