FreeRDP: [server terminates connection] Upgrading from 2.x to 3.x SSL read errors after connect
Describe the bug
I’m connecting from Manjaro Linux laptop to Windows Server 2016 Standard using Remmina with RDP protocol. Windows server is a part of the domain, but my laptop is not a part of domain (that’s important). NLA security protocol is used.
When using FreeRDP 2.11.4 everything is fine: freerdp2_nla.txt
Few days ago Manjaro package freerdp was upgraded:
[2024-04-04T21:42:27+0300] [ALPM] upgraded freerdp (2:2.11.4-1 -> 2:3.4.0-5)
After upgrade RDP connections started to fail: freerdp3_nla.txt
FreeRDP 3.x started using Kerberos for NLA security scheme, but my laptop is not a part of domain, it does not have properly configured /etc/krb5.conf. kinit command is failing with the same error Cannot find KDC for realm "MYREALM" as the RDP does.
To Reproduce Internal network, cannot provide full connection description.
Expected behavior
Users should be able to connect to Windows Server with domain, without adding device there RDP client is running to the same domain. As it was on FreeRDP 2.x.
Screenshots
Application details
- FreeRDP version (
xfreerdp /version): libfreerdp 3.4.0 - Command line used: -
- Output of
xfreerdp /buildconfig: - - OS version connecting to (server side): Windows Server 2016 Standard
- If available the log output from a run with
/log-level:trace 2>&1 | tee log.txt: see above - If you built it yourself add some notes which tag/commit/branch you have used, also your cmake parameters and compiler can help
Environment (please complete the following information):
- OS: [e.g. Linux/Windows/Android/…]: Manjaro with Linux kernel 6.8.4-1
- Version/Distribution: [e.g. Debian 10, Windows 2008, Android 10]
- Architecture: [amd64, arm]: x86_64
Additional context
Thank you for reporting a bug!
About this issue
- Original URL
- State: closed
- Created 3 months ago
- Comments: 25 (25 by maintainers)
@dolfinus
xfreerdporsdl-freerdp?buildconfig?remminaas well? (I don´t think the old version can handleFreeRDP3)I suspect a
remminabug with newfreerdp3as there have been many changes and some might have been missed. (did just successfully connect to our test domain withxfreerdp)