[
https://issues.apache.org/jira/browse/GUACAMOLE-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558276#comment-17558276
]
Nick Couchman commented on GUACAMOLE-1627:
------------------------------------------
Also, it seems like adding this option would only work if the user happened to
be running a very specific version of FreeRDP that also supports this setting -
a feature merged into the FreeRDP master branch in the past 24 hours, so not
likely to make it into the packages included with most distributions for months.
I guess I'm not completely opposed to it if others feel it should be added, but
it seems like the wrong way of solving the problem - aren't the better options
either 1) get Microsoft to patch Server 2019 (since it's confirmed that Server
2022 already functions correctly), or 2) disable TLS v1.3 support in Server
2019, since the patch to FreeRDP just forces TLS down to v1.2?
> Gucamole can't conect to a windows 2019 server when both TLS1.2 and TLS1.3
> are enabled
> --------------------------------------------------------------------------------------
>
> Key: GUACAMOLE-1627
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1627
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server
> Affects Versions: 1.4.0
> Reporter: siva
> Priority: Major
>
> The FreeRDP lib, which gucamole depends on for RDP connections, fails to
> perform a proper handshake with a windows 2019 server when both TLS1.2 and
> TLS1.3 are enabled. A fix has been put in the FreeRDP lib (see Github link in
> External issue URL) to enforce TLSv1.2 during connection handshake.
> Gucamole server project needs to target the version of FreeRDP that has this
> fix.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
