* Implemented missing server side version of PDU (just skip data)
* Refactored read/write functions to properly check stream
length/capacity and handle return values.
(cherry picked from commit ec3c333656b4d8a00ff278a70b52c11b18e2d643)
If a request was pending and new formats were announced the response
to a ServerFormatDataRequest was never sent.
(cherry picked from commit 2efb7d92745614a92c66b721205689a433248d31)
Most GFX graphics do not carry alpha data. Keep the original
alpha value unless specified otherwise.
(cherry picked from commit 115532ef5a71676a946c9d268dd1294daf99e52d)
Input events are only allowed after a connection was established
(connection state is active)
This check aborts input sending when done before that.
(cherry picked from commit 102869f6a860140174da9dd3189babf6966c9149)
Currently, non-zero exit code is returned for /version, /buildconfig, /help,
/monitor-list, /kbd-list and /kbd-lang-list command-line options for several
clients. This is against conventions because 0 is usually returned in
such cases. Also, there is potentially another problem that the returned
codes overflow on UNIX systems (where the exit code is a number between 0
and 255). Let's fix the clients to return 0 in the mentioned cases to honor
conventions and 1 for the command-line parsing errors (or -1 for clients
who already use that value).
Fixes: https://github.com/FreeRDP/FreeRDP/issues/6686
(cherry picked from commit 3ee4cabcfad3a9ccc3c59be21245b57c17e7ae75)
some hotplug implementations report the same drive multiple times.
to avoid redirecting the same drive multiple times check if it is
already in the list before adding.
(cherry picked from commit 9e8d3fbbf5ad7bb75799a8aca9fafa9c2dcf7fd9)
This PR removes the error code from the error string returned by
rpc_error_to_string. The error code is passed into the function so it is
not necessary to append it to the returned string as well.
The PR also fixes the screwed formatting of the error code tables.
(cherry picked from commit c78566d2a239648087949dc4ae58e18093f8bf6c)
Currently, when a local uri-list is converted into a FILEDESCRIPTORW
list, WinPR doesn't submit the last write time for each file.
The result of this is that the last write time of each file on the
other peer will have the current time and not the actual last write
time that is present on the peer, where the files were copied from.
Fix this by also writing the last write time in addition to the
FD_WRITESTIME flag.
(cherry picked from commit 9ba614a1e3314d9d3daa6e461e7d360c67c8d000)
As discussed in #4717 allow autoreconnect to succeed if that
specific error code was returned as disconnection reason.
(cherry picked from commit 552a7ca25f60e9a00585ec298c816911dcf71383)
* cached brush orders missed the BMF_24BPP documented case
([MS-RDPEGDI] 2.2.2.2.1.2.7)
* add some comments on secondary (brush) order details
(cherry picked from commit efdc99528f6fb6d56537a5420bfa8e735219eba0)
