From NetDrive 3.4 we use WinSSL for secure connections. WinSSL is provided by Microsoft.
If your sshd server does not work with WinSSL, you need to add following line to your /etc/ssh/sshd_config file.
Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc
If your sshd_config already has Ciphers config, add following items:
aes128-cbc, 3des-cbc, blowfish-cbc, cast128-cbc,aes192-cbc,aes256-cbc
Restart sshd using following command:
service sshd restart
To implement secure communications, NetDrive needs to connect with a library that handles the SSL (secure socket layer) encryption. On Linux and Macs, NetDrive uses the OpenSSL library, which is included on those systems. Windows doesn’t have this library (at least, outside of the Subsystem for Linux), so on Windows previous versions of NetDrive included the OpenSSL library and associated certificate.
Recent OpenSSL versions have compatibility issues with Qt library which we use as our GUI toolkit. Qt recommends to use older version of OpenSSL to go around the compatibility issue but old versions of OpenSSL have many security issues which must be avoided.
Now we uses WinSSL for secure communications. This means NetDrive uses the same security architecture as other connected applications on Windows and WinSSL shows better performance than OpenSSL on Windows as we tested.