akallabeth

Relevant specifications are `[MS-RDPEDP]` and `[MS-RDPEDP2]`

@monkeytreehosting yes, that are the specs. Thing is the transport layer will need major modifications for this.

Please try the following: 1. If you are really using `freerdp-proxy`: in `2.0` series it was a bleeding edge module, it has been extensively refactored and improved in current `master`,...

@ionlionsion interesting issue. We´d require some additional information to categorize: 1. Does this work if you use `mstsc` (e.g. the microsoft RDP client) the way you think it should? 2....

@ionlionsion ok, then can you try with https://flathub.org/apps/details/com.thincast.client ? it also supports rails and is based on FreeRDP, so would be interesting to know if this is a `xfreerdp` issue...

@ionlionsion ok, so it is a `xfreerdp` bug related to input handling :/ Thanks for the update.

@ionlionsion can´t give any schedule, but it will eventually be fixed.

@hardening that would break the API as `REGION16_DATA` is exposed. Restructured it this way to avoid the hack (free on const data) and simplify tests while keeping compatibility with 2.1.2

@freerdp-bot test

@chrislong is this still the case with our nightly builds? There have been a few fixes targeted at rail support.