The peer context memory block should not be freed by the server
implementation because it still needs to be accessed after the
context free callback has been called. It should be the core's
responsibility to free it.
According to the specification first two bytes contain keyboardFlags.
Those keyboardFlags are a bit different than in the regular (non-unicode)
Keyboard Event. There is no KBD_FLAGS_EXTENDED here and also when
key is pressed there is neither KBD_FLAGS_DOWN nor KBD_FLAGS_RELEASE flag
set. When key is released the KBD_FLAGS_RELEASE flag is set.
Moving the osMajorType and osMinorType settings to the client so that the
client can set a real os type constant. This will give a more useful hint
to the server.
- pcap_open did not return NULL if fopen failed
- libfreerdp-core, tfreerdp-serer and xfreerdp-server did not check the pcap_open result
- also fixed the sleep calculation in the xfreerdp-server
pcap used utils/stopwatch to save a record's timestamp which is not suitable because stopwatch measures cpu time and not the wall-clock time
also fixed the sleep calculation in the tfreerdp test server
