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 Fast-Path Input Event PDU has the following basic structure (sections 5.3.8 and 5.4.4):
fpInputHeader: Fast-Path Input Header (section 2.2.8.1.2)
length1 and length2: Packet length (section 2.2.8.1.2)
fipsInformation: Optional Fast-Path FIPS Information (section 2.2.8.1.2)
dataSignature: Optional data signature (section 2.2.8.1.2)
numEvents: Optional number of events (section 2.2.8.1.2)
PDU contents (collection of input events):
Keyboard Event (section 2.2.8.1.2.2.1)
Unicode Keyboard Event (section 2.2.8.1.2.2.2)
Mouse Event (section 2.2.8.1.2.2.3)
Extended Mouse Event (section 2.2.8.1.2.2.4)
Synchronize Event (section 2.2.8.1.2.2.5)
Quality Of Experience (QOE) Timestamp Event (section 2.2.8.1.2.2.6)
Relative Mouse Event (section 2.2.8.1.2.2.7)
If Enhanced RDP Security (section 5.4) is in effect, the External Security Protocol (section 5.4.5) being used to secure the connection MUST be used to decrypt and verify the integrity of the entire PDU prior to any processing taking place.
The contents of the embedded action field of the fpInputHeader field MUST be set to FASTPATH_INPUT_ACTION_FASTPATH (0). If it is not set to this value the PDU is not a Fast-Path Input Event PDU and MUST be processed as a slow-path PDU (section 3.3.5.2).
If the embedded flags field of the fpInputHeader field contains the FASTPATH_INPUT_ENCRYPTED (2) flag, then the data following the optional dataSignature field (which in this case MUST be present) MUST be verified and decrypted using the methods and techniques described in section 5.3.6. If the MAC signature is incorrect or the data cannot be decrypted correctly, the connection SHOULD be dropped. If Enhanced RDP Security is in effect and the FASTPATH_INPUT_ENCRYPTED (2) flag is present the connection SHOULD be dropped because double-encryption is not used within RDP in the presence of an External Security Protocol Provider.
The numEvents field details the number of input events present in the fpInputEvents field. The input events present in this field MUST be interpreted and processed according to the descriptions detailed from sections 2.2.8.1.2.2.1 through 2.2.8.1.2.2.5. If a Fast-Path Input Event structure is received that does not match one of the known types, the server SHOULD drop the connection.
Once this PDU has been processed, the server MUST inject the input event into the user's session.