SSH2 only instead of SFTP over SSH2?

[marlon]

Does FZ support SSH2 only instead of SFTP over SSH2?

More and more hosters seem to prefer SSH2 only (meaning FTP using an SSH2 tunnel) as a replacement for SFTP over SSH2. Thanks for your help in advance!

Marlon

[botg]

I've never heard about such a thing.

[marlon]

You have never heard of FTP over an encrypted SSH2 connection?

Marlon

[eddan]

Actually I've heard it mentioned in the sf.net forums and tried googling it, but it didn't help me figure out the difference. Maybe you could post a link to where this is explained marlon?

[marlon]

"CuteFTP Professional supports SFTP, which is a secure service provided by the SSH2 host, in which the server both encrypts the data and handles the file transfer. This should not be confused with FTP over SSH2, in which the SSH2 uses it's "port forwarding capabilities to forward standard FTP transactions over an encrypted tunnel, with the actual file transfer being handled by a separate (and non-secure) FTP server." (found at http://www.cuteftp.com/cuteftpprob/tour_2.asp)

With some more googling, I found another page with a few bits of information: http://www.itc.virginia.edu/desktop/sec ... ml#diagram.

Marlon

[botg]

That's just standard port forwarding/tunneling, it's not very useful to use ftp over this, especially since files have to be transferred twice: First to the SSH server then to the ftp server. SFTP is a much better solution.

[veridian_33]

Opening this very old post once more, I have noticed that there are some problems in Filezilla 3.0.3 with SFTP. I've checked the forum for similar posts, however did not found anything more similar than this.

The situation:
I'm connecting to an Solaris 10 server, running SSH2 daemon. The server is actually a clustered node (two Solaris 10 machines, each having its own IP address and the node itself having a VIP address; the situation is the same when connecting to VIP or the physical addresses)
I have to use a port forwarding to connect to the node.

Now the problem:
- using Filezilla 2.2.9 and servertype "SFTP using SSH2", I am able to connect normally.
- when using Filezilla 3.0.3 (and previous 3.0.x releases), servertype is set to "SFTP - SSH file transfer protocol" as there is no "SFTP using SSH2" anymore. I am unable to connect due to a timeout. The connection log follows:

Status: Selected port usually in use by a different protocol.
Status: Connecting to localhost:8901...
Trace: Going to execute E:\download\appz\FileZilla_3.0.3_win32\FileZilla-3.0.3\fzsftp.exe
Response: fzSftp started
Trace: CSftpControlSocket::ConnectParseResponse(fzSftp started)
Command: open "root@localhost" 8901
Trace: Looking up host "localhost"
Trace: Connecting to 127.0.0.1 port 8901
Trace: Server version: SSH-2.0-Sun_SSH_1.1
Trace: Using SSH protocol version 2
Trace: We claim version: SSH-2.0-PuTTY_Local:_Nov__7_2007_01:50:23
Trace: Doing Diffie-Hellman group exchange
Trace: Doing Diffie-Hellman key exchange with hash SHA-1
Trace: Host key fingerprint is:
Trace: ssh-rsa 1024 f9:75:19:3c:25:b1:61:0d:60:4c:a3:2f:6c:5412
Trace: Initialised AES-128 SDCTR client->server encryption
Trace: Initialised HMAC-SHA1 client->server MAC algorithm
Trace: Initialised AES-128 SDCTR server->client encryption
Trace: Initialised HMAC-SHA1 server->client MAC algorithm
Error: Connection timed out
Trace: CSftpControlSocket::ResetOperation(2114)
Trace: CControlSocket::ResetOperation(2114)
Error: Could not connect to server
Status: Waiting to retry...

I've compared the output logs from Filezilla 2.2.9 and 3.0.x and they look the same up to the point "HMAC-SHA1 server->client MAC algorithm". After this point, Filezilla 2.2.9 receives

I have tried to connect with PuTTYs PSFTP manually and it works normally.

Also, I've noticed that Filezilla 3.0.3 (and previous 3.0.x versions) seem to have a lower timeout value set up when connecting. Namely, when using the old Filezilla 2.2.9, I am able to connect to the server in approx 22 seconds each time. Filezilla 3.0.x gives me a timeout after approx 17.5 seconds (leading me to believe that it could connect successfully if the timeout was increased)?

Is there any way to increase this timeout? Or do you have any other tip I could try?

Just for convenience, here is the connection log from Filezilla 2.2.9:

Status: Connecting to localhost:8901 ...
Trace: FzSFtp.exe: FzSFtp started and initialized.
Trace: SftpControlSocket.cpp(2303): OnConnect(0) caller=0x00e25fcc
Status: Connected with localhost:8901, initializing SFTP connection...
Command: CONNECT root@localhost:8901
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: FzSFtp.exe: Ssh.c(2117): Server version: SSH-2.0-Sun_SSH_1.1
Trace: FzSFtp.exe: Ssh.c(2153): We claim version: SSH-2.0-PuTTY-FZ-Local: Oct 27 2004 19:41:19
Trace: FzSFtp.exe: Ssh.c(2155): Using SSH protocol version 2
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: FzSFtp.exe: Ssh.c(4520): Doing Diffie-Hellman group exchange
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: FzSFtp.exe: Ssh.c(4548): Doing Diffie-Hellman key exchange
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: FzSFtp.exe: Ssh.c(4605): Host key fingerprint is:
Trace: FzSFtp.exe: Ssh.c(4606): ssh-rsa 1024 f9:75:19:3c:25:b1:61:0d:60:4c:a3:2f:6c:5412
Trace: FzSFtp.exe: Ssh.c(691): Initialised AES-128 client->server encryption
Trace: FzSFtp.exe: Ssh.c(691): Initialised AES-128 server->client encryption
Trace: FzSFtp.exe: Ssh.c(691): Initialised HMAC-SHA1 client->server MAC algorithm
Trace: FzSFtp.exe: Ssh.c(691): Initialised HMAC-SHA1 server->client MAC algorithm
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: FzSFtp.exe: Ssh.c(5001): Access granted
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: FzSFtp.exe: Ssh.c(5699): Opened channel for session
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: FzSFtp.exe: Ssh.c(6147): Started a shell/command
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Response: Remote working directory is /root
Status: Connected
Trace: SftpControlSocket.cpp(2421): ResetOperation(1) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",1) caller=0x00e25fcc
Status: Retrieving directory listing...
Command: PWD
Response: Remote directory is /root
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",0) caller=0x00e25fcc
Command: LIST
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(2594): OnReceive(0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",0) caller=0x00e25fcc
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",0) caller=0x00e25fcc
Response: Sucessfully received 7 items
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",0) caller=0x00e25fcc
Status: Directory listing successful
Trace: SftpControlSocket.cpp(2421): ResetOperation(1) caller=0x00e25fcc

Cheers,
veridian_33

[botg]

Check the settings dialog for the timeout option.

[veridian_33]

Thank you botg! (missed that config option...)

Now it's working.

Cheers,
veridian_33