Current implementation of DeviceRedirectionMITM can lead to request collision, leading to unpredictable behavior

[Res260]

The current implementation of the DeviceRedirectionMITM only stores the requestID when a packet is received. This requestID is stored by PyRDP to look for specific types of anwsers.

However, the requestID is not unique and can be used by other devices, which PyRDP doesnt take into account. PyRDP should store a pair of deviceID, requestID instead of simply requestID.

I am unsure of the current impact of this. It probably can raise KeyErrors leading to the packet not being forwarded.