Question removed.
And this field doesn't seem to be used at all.
12.01.23 08:12, Andrey Vasilkin via FreeRDP-devel пишет:
Hi.
libwinpr/synch/synch.h, line 130:
struct sched_param param;
The structure sched_param is not described anywhere.
___
It seems that the problem is not stable. Now, after successfully
connecting with the old version, the new version is also connected, the
problem is not reproduced. :-/
If (when) the situation comes back, I'll try -sec:rdp.
12.01.23 09:06, Eric Brown via FreeRDP-devel пишет:
Andrey,
It looks
Andrey,
It looks like the correct option to force RDP level encryption is:
-sec:rdp
Eric
On Wed, Jan 11, 2023 at 4:00 PM Andrey Vasilkin via FreeRDP-devel <
freerdp-devel@lists.sourceforge.net> wrote:
> I've try switch "-encryption" without any results - log is same.
>
> Then, I've get
I've try switch "-encryption" without any results - log is same.
Then, I've get version builded 2022-09-16. No any problems:
[08:54:47:710] [7620:029ceb60] [WARN][com.freerdp.core.nego] - Error:
SSL_NOT_ALLOWED_BY_SERVER
[08:54:47:714] [7620:029ceb60] [WARN][com.freerdp.core.nego] - Error:
If you can install and run the previous version of the client that worked
and capture the log from a successful connection, it will tell a lot (and
also verify that it isn't something that changed on the server).
I don't know enough about the current state of FreeRDP to know offhand if
something
Hi.
libwinpr/synch/synch.h, line 130:
struct sched_param param;
The structure sched_param is not described anywhere.
___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
