Hi all!
First Bazzite is just crazy ! I come from Windows environment, but happy to begin with linux and Bazzite.
I have an issue to remote control my Legion Go with Bazzite from a WIN11Pro PC.
I configure everything in Bazzite, user & password, opened Firewall with RDP, auto certificate etc… and then relaunch the RDP service.
But when i try to connect from my Win11 Computer, i can find the device with IP or computer name, enter my login (until this step everything’s fine), and when i validate my credentials then it seems negotiating with the certificate and nerver connect to my remote desktop Legion go. I have no error message… Just the RDP connection is in progress but never stop or time out with “Securing remote connection” progresse…
If someone ever had this probleme or could help i’ll be glad ?!
Thx a lot a see ya !
I had the same issue using a linux client (GNOME Connections) but I found a workaround. Since you’re using Windows as a client it won’t work unfortunately but since my error was a certificate error, maybe you can find a way to get the certificate from krdp and put it on your client ?
I was able to connect with FreeRDP though. So I launched flatpak run org.gnome.Connections and I noticed that it was hanging because of an error with the certificate :
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_certificate_name_mismatch_error]: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_certificate_name_mismatch_error]: @ WARNING: CERTIFICATE NAME MISMATCH! @
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_certificate_name_mismatch_error]: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_certificate_name_mismatch_error]: The hostname used for this connection (192.168.1.95:3389)
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_certificate_name_mismatch_error]: does not match the name given in the certificate:
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_certificate_name_mismatch_error]: Common Name (CN):
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_certificate_name_mismatch_error]: no CN found in certificate
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_certificate_name_mismatch_error]: A valid certificate for the wrong name should NOT be trusted!
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_new_certificate_warn]: The host key for 192.168.1.95:3389 has changed
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_new_certificate_warn]: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_new_certificate_warn]: @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_new_certificate_warn]: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
[12:01:40:253] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_new_certificate_warn]: IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
[12:01:40:254] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_new_certificate_warn]: Someone could be eavesdropping on you right now (man-in-the-middle attack)!
[12:01:40:254] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_new_certificate_warn]: It is also possible that a host key has just been changed.
[12:01:40:254] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_new_certificate_warn]: The fingerprint for the host key sent by the remote host is b3:0e:d8:5e:a3:a2:ec:98:7e:eb:64:cf:8f:42:45:b6:92:02:9a:84:c4:c6:4a:71:27:dc:7d:71:cb:92:f2:97
[12:01:40:254] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_new_certificate_warn]: Please contact your system administrator.
[12:01:40:254] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_new_certificate_warn]: Add correct host key in /var/home/lou/.var/app/org.gnome.Connections/config/freerdp/server/192.168.1.95_3389.pem to get rid of this message.
[12:01:40:254] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_new_certificate_warn]: Host key for 192.168.1.95 has changed and you have requested strict checking.
[12:01:40:254] [2:00000002] [ERROR][com.freerdp.crypto] - [tls_print_new_certificate_warn]: Host key verification failed.
Since I had the certificate from my previous FreeRDP connection I was able to put it in the right place and now Connections is able to connect properly.