Devolutions ForumDevolutions Forum

Unable to connect to data source

Resolved

Unable to connect to data source

avatar
dsi1

Hello,

I have 2 users who are using the Linux version of RDM, and both cannot connect to the datasource. When they click on "Test Host", they get the following message:
forum image

The datasource is a Microsoft SQL server database. The connection works fine for Windows users.

It seems the problem appeared after updating Ubuntu OS from 18.04 and 20.04 to 22.04 for both users. They also both have the latest version of RDM (2022.3.1.3).

All Comments (4)

avatar
Jonathan Lafontaine

Hi,

It might be related to .net6 security feature disabling TLSv1 by default.
If that is the case, these steps should let you connect.

In /etc/ssl/opensll.cnf
Place this at the top of the file

openssl_conf = default_conf


You can place this in the file, doesn’t matter where. 

[ default_conf ]
ssl_conf = ssl_sect

[ ssl_sect ]
system_default = system_default_sect

[ system_default_sect ]
MinProtocol = TLSv1
CipherString = DEFAULT@SECLEVEL=1


Let me know if this helps.
Regards

Jonathan Lafontaine

avatar
dsi1

Thanks for your reply (and sorry for the delay).

Your configuration as you gave it don’t work for me. I had to put CipherString = DEFAULT@SECLEVEL= 0 instead of 1, and then, it worked fine.

However, I'm not sure about the security implications of this setting…

avatar
Jonathan Lafontaine

CipherString = DEFAULT@SECLEVEL=0 means every cipher is accepted.
1 is minimum 80 bytes cipher, 2 is 112 bytes and level 5 is 256.

0 also remains compatible with previous version of OpenSSL.
It's not ideal but you can't be more secure than your SQL server.

You could however use this SSL config only for RDM.

  1. Copy /etc/ssl/openssl.cfg to your home folder
  2. Revert the changes in the original files
  3. create a new startup script for RDM and use export OPENSSL_CONF=~/.openssl.cnf before calling remotedesktopmanager


Let me know if this helps.
Regards

Jonathan Lafontaine

avatar
dsi1

Thank you Jonathan for your help,

I haven't tried what you explained to me. We finally decided to install a new up-to-date Windows and SQL server to improve overall security. We have moved the database to this new server. All has been working fine since, even with the security level = 2.

Thanks again