SFTP not working

[andzej-telican]

After update NetDrive version stop working all SFTP connections, FTP work
[ERROR ] [ 8744] [SERVICE ] [ nd3 sdk version - child nd3svc : 3.4.384 ] [Child.cpp:132]

[jyyoon]

ter update NetDrive version stop working all SFTP connections, FTP work

[ERROR ] [ 8744] [SERVICE ] [ nd3 sdk version - child nd3svc : 3.4.384 ] [Child.cpp:132]

After setting the log level to VERBOSE, please reproduce the problem and send us the debug log file :

How to attach a log file

Change Log Level First, check your settings and change log level to VERBOSE. Go to Settings: [image] Change log level to VERBOSE: [22] Set to DEBUG if you use old version because there is no VERBOSE log level. Get back to DRIVES screen Changed log level takes effect when you leave SETTINGS screen. Reproduce your problem ! After changing log level you must repeat your steps to reproduce the problem you have. This time it will be logged in relevant log files. Send Log File Within your driv…

Sorry for the inconvenience it may caused.

[francyci]

Maybe related to the problem I am having?

The latest version seems to be missing many of the ciphers supported in earlier versions.

Recent 3.4.384 update has broken SFTP (missing ciphers)

With the recently updated 3.4.384 Netdrive SFTP connections fail. On the client when attempting to connect you get an error “name : Connection Error”. From the ssh server we now get this error. Mar 14 15:04:04 do-cm-01 sshd[186736]: Unable to negotiate with {{fullip}} port 53013: no matching cipher found. Their offer: aes256-cbc,rijndael-cbc@lysator.liu.se,aes192-cbc,aes128-cbc,arcfour128,arcfour,3des-cbc [preauth] A successful connection from 3.4.369 used aes128-ctr. sshd[186347]: debug1…

[support1]

@andzej-telican @francyci

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.