I began some work on a rudimentary (not yet working) version of this. I'm at a point where I need to implement a `remdesk` channel as defined here https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-ra/d16f1722-0422-41c4-8b64-d1fd9479e0c2 as well as a `encomsp` channel.
A bit more involved than I initially thought, but a good exercise diving and studying Guac code. I noticed some recent threads on FreeRDP3, including the RAIL issue - so I'm currently working on FreeRDP3 support in line with recent efforts. This is probably the wrong thread / board for this discussion moving forward. If I get a working version up and running, I'll post the update and share my fork on the dev maillist. - Robert On Sat, Aug 16, 2025 at 6:13 AM Nick Couchman <[email protected]> wrote: > On Fri, Aug 15, 2025 at 6:50 PM Robert Devitt <[email protected]> wrote: > >> >> It might be a bit challenging to implement since you have to take a >>> invite file and parse that out, >> >> >> Here's the relevant section for parsing logic for freerdp - >> >> https://github.com/FreeRDP/FreeRDP/blob/d8aff4aa1d177ba6a2d5102d55c1c062ede8b7ec/client/common/client.c#L407 >> <https://github.com/FreeRDP/FreeRDP/blob/d8aff4aa1d177ba6a2d5102d55c1c062ede8b7ec/client/common/client.c#L407> >> >> And here is some official documentation on the Invitation file format - >> https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rai/ac87f4ab-859e-4eb9-a05e-7bbf7f1bc868 >> >> > Brilliant, thank you! > > -Nick > >> -- Robert Devitt [email protected]
