I upgraded my Directory Opus licenses to support SFTP. I am facing many issues getting SSH FTP to work. The private key generated by my web server added under my .ssh folder appears to not be supported by Directory Opus. I converted it to PuTTY's format via Pageant and entered the correct password for it. I am able to establish a connection to the web server, but I will later see access denied with all activity. Directory Opus is doing weird things like attempting to cd to root directory that it does not have access to. Also, navigating to one directory successfully results in weird errors when I click the parent directory button. I am getting access denied with all activity. It's really weird and looks broken.
Cyberduck using the same private key works without issue for all activity, but Directory Opus is having major issues.
I just established a successful connection. Here's logs:
Opening Connection ftp.randomserver.com:22
Server version: SSH-2.0-OpenSSH_7.4
Using SSH protocol version 2
We claim version: SSH-2.0-PuTTY_Directory_Opus
Server supports delayed compression; will try this later
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-256
Server also has ecdsa-sha2-nistp256/ssh-dss/ssh-rsa host keys, but we don't know any of them
Host key fingerprint is:
ssh-ed25519 256 7b:f7:48:21:4f:4a:36:0d:8c:f3:c5:cb:23:fe:0f:0a
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA-256 client->server MAC algorithm
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA-256 server->client MAC algorithm
Reading key file "C:\Users\Jamil\.ssh\id_rsa"
Unable to use this key file (OpenSSH SSH-2 private key (old PEM format))
Unable to use key file "C:\Users\Jamil\.ssh\id_rsa" (OpenSSH SSH-2 private key (old PEM format))
Pageant is running. Requesting keys.
Pageant has 1 SSH-2 keys
Using username "randomusername".
Trying Pageant key #0
Authenticating with public key "
imported-openssh-key
" from agent
Sending Pageant's response
Access granted
Initiating key re-exchange (enabling delayed compression)
Opening session as main channel
Server supports delayed compression; will try this later
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-256
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA-256 client->server MAC algorithm
Initialised zlib (RFC1950) compression
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA-256 server->client MAC algorithm
Initialised zlib (RFC1950) decompression
Opened main channel
Started a shell/command
SSH: CTS CONNECTED
SSH: Listing Directory
SSH: List complete 33 files.
If I then double click a directory shown followed by clicking the parent button, trouble starts:
Opening Connection ftp.randomserver.com:22
Server version: SSH-2.0-OpenSSH_7.4
Using SSH protocol version 2
We claim version: SSH-2.0-PuTTY_Directory_Opus
Server supports delayed compression; will try this later
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-256
Server also has ecdsa-sha2-nistp256/ssh-dss/ssh-rsa host keys, but we don't know any of them
Host key fingerprint is:
ssh-ed25519 256 7b:f7:48:21:4f:4a:36:0d:8c:f3:c5:cb:23:fe:0f:0a
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA-256 client->server MAC algorithm
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA-256 server->client MAC algorithm
Reading key file "C:\Users\Jamil\.ssh\id_rsa"
Unable to use this key file (OpenSSH SSH-2 private key (old PEM format))
Unable to use key file "C:\Users\Jamil\.ssh\id_rsa" (OpenSSH SSH-2 private key (old PEM format))
Pageant is running. Requesting keys.
Pageant has 1 SSH-2 keys
Using username "randomusername".
Trying Pageant key #0
Authenticating with public key "
imported-openssh-key
" from agent
Sending Pageant's response
Access granted
Initiating key re-exchange (enabling delayed compression)
Opening session as main channel
Server supports delayed compression; will try this later
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-256
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA-256 client->server MAC algorithm
Initialised zlib (RFC1950) compression
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA-256 server->client MAC algorithm
Initialised zlib (RFC1950) decompression
Opened main channel
Started a shell/command
SSH: CTS CONNECTED
SSH: Listing Directory
SSH: List complete 33 files.
Connection closed
Opening Connection ftp.randomserver.com:22
Server version: SSH-2.0-OpenSSH_7.4
Using SSH protocol version 2
We claim version: SSH-2.0-PuTTY_Directory_Opus
Server supports delayed compression; will try this later
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-256
Server also has ecdsa-sha2-nistp256/ssh-dss/ssh-rsa host keys, but we don't know any of them
Host key fingerprint is:
ssh-ed25519 256 7b:f7:48:21:4f:4a:36:0d:8c:f3:c5:cb:23:fe:0f:0a
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA-256 client->server MAC algorithm
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA-256 server->client MAC algorithm
Reading key file "C:\Users\Jamil\.ssh\id_rsa"
Unable to use this key file (OpenSSH SSH-2 private key (old PEM format))
Unable to use key file "C:\Users\Jamil\.ssh\id_rsa" (OpenSSH SSH-2 private key (old PEM format))
Pageant is running. Requesting keys.
Pageant has 1 SSH-2 keys
Using username "randomusername".
Trying Pageant key #0
Authenticating with public key "
imported-openssh-key
" from agent
Sending Pageant's response
Access granted
Initiating key re-exchange (enabling delayed compression)
Opening session as main channel
Server supports delayed compression; will try this later
Doing Diffie-Hellman group exchange
Doing Diffie-Hellman key exchange with hash SHA-256
Initialised AES-256 SDCTR client->server encryption
Initialised HMAC-SHA-256 client->server MAC algorithm
Initialised zlib (RFC1950) compression
Initialised AES-256 SDCTR server->client encryption
Initialised HMAC-SHA-256 server->client MAC algorithm
Initialised zlib (RFC1950) decompression
Opened main channel
Started a shell/command
SSH: CTS CONNECTED
SSH: Listing Directory
SSH: List complete 2 files.
SSH: Directory /var/log/apache2/domlogs: permission denied
SSH: Directory /var/log/apache2: permission denied
SSH: Directory /: permission denied
SSH: Directory /: permission denied
SSH: Directory /: permission denied
SSH: Directory /: permission denied
It’s saying access to other directories is denied before it goes to the root. It’s probably only going to the root because it is unable to go to where it has been told to, and it falls back on the root/parents to try to show something.
Okay. This same issue happens when navigating to any and all folders under my home directory. Something is not working with SFTP access for Directory Opus. Per the logs, it shows that two files were retrieved from the directory listing post navigation. Traversing back seems to cause the issue.
I played around more with this in an attempt to figure out what is going wrong here.
What appears to be happening is that Directory Opus is losing track of the current directly only when the Go Up button is pressed. In my log example above it shows this:
The code for some reason believes the current path is /var/log/apache2/domlogs, but the current directory remains at ~/logs. The current directory will then remain incorrect for the remainder of the time the lister is open. It remains incorrect even after the connection is closed. The only way to correct it is to close Directly Opus. I see no way to force a disconnect from the SFTP server.
I did install the latest BETA, and this issue remains present. (12.30.1)
What happens if you set the Initial Directory for the site/bookmark to blank, then navigate to your home directory from there? Does going up at that point then work?
Or if you set it to the absolute path to the home directory (not the ~ alias, which could be confusing things somewhere)?
The initial directory has an absolute path and does not use ~. I only typed ~ here as a shortcut.
/home2/jamil
I think I see what is going on now. The unix server has a symlink. There is a logs directory and an access-logs directory. I was clicking logs before, and it is an empty directory. access-logs links to: var/log/apache2/domlogs/jamil. The Go Up button is attempting to navigate to var/log/apache2/domlogs that I do not have permission to. The Go Back button navigates to the previous directory and works properly.
The logs directory is completely empty, so this beta version I am using now may have resolved the issue related to this. I was previously double clicking logs that is not a symlink but an empty directory. The previous version was not navigating to the correct directory (possibly due to it being completely empty).
To add to my confusion, Cyber Duck that I also use as an FTP client has different behavior. I can double click access-logs under Cyber Duck (and Mountain Duck) followed by clicking up to navigate from:
home2/jamil
to
home2/jamil/access-logs
and back again. The two ftp clients handle symlinks very differently.
When I use putty to ssh to the web server shell from my home directory, I see the following behavior:
[~]# cd access-logs
[~/access-logs]# cd ..
[~]#
You may wish to reconsider navigating to full paths from a symlink (or at least add an option to turn that off). It's unusual handling.