I understand that.
You can connect to the server using dolphin file manager - IF you do as I have described above.
I understand that.
You can connect to the server using dolphin file manager - IF you do as I have described above.
Yes, i checked (few times now). It’s the same (and no different when it was setup).
As i wrote:
That ^^^ is a description what i see on the screen.
I also saved the link you posted:
It has a command to log Dolphin.
Will try that at a later date.
Thanks
Just to confirm, you get this window:
/path/to/key And no other popup for a user or password.
If so, that tells me ksshpass is already installed. And you probably need to set one variable for it to work: $SSH_ASKPASS.
It may have hung up at that step, and never got to the next step with the password.
The blog I linked mentioned this variable, but here’s an Arch Wiki link doing the same thing:
https://wiki.archlinux.org/title/KDE_Wallet#Using_the_KDE_Wallet_to_store_ssh_key_passphrases
Just assigning at least one variable in: ~/.config/environment.d
I do not use encrypted key, so no need for a passphrase.
The steps are simple, so again:
Server requires key AND user password.
The window that does not come up is the window asking for the user password.
I tried logging what is described in:
The log shows that the key is accepted by the server and then fails which is correct because Dolphin never shows the prompt for the user password.
On the cli it works flawlessly, both ssh and sftp.
But i now tried with
fish://username@IP
in Dolphin and it works flawlessly.
So it still seems something is wrong with Dolphin, or whatever layer underneath it, that handles sftp.
I followed @linux-aarhus’s post and dolphin asks for my key’s passphrase then the user’s password.
However I’m on unstable.
![]()
Yes - that is clear.
So the credentials is
Even if you configure your ~/.ssh/config Host entry with a username - the username should be specified as described above
Enter the connection string specifying the user sftp://user@server
It is normal to get message about the host signature if/when you change the Host entry in the configuration - the message is harmless - it simply tells you that the host is now known with one more name.