I access ServerB using LoginB via a login node called ServerA using LoginA. The servers are configured an ssh-keys in my .ssh/config. To reach ServerB a ProxyCommand is used (ssh -W). This works flawlessly on the console with ssh. "ssh ServerB" hops transparently (as my keys are in the ssh-agent) over ServerA and logs me into ServerB.

When I now open fish://ServerA in f.ex. kwrite, it switches to the local home and shows my files. Good ;-). But opening fish://ServerB fails as it tries to log into the server with the wrong username. It should use the login as given via the User directive in the .ssh/config. Entering my ServerB-login with password in the now showing dialog box works. So using ServerA as a proxy works. The problem is just kio_fish not respecting the User name.

This is a minor annoyance in this case, as I am able to provide a login with password for ServerB. But in many cases this isn't possible as the logins are based on ssh-key only.

Reproducible: Always

Steps to Reproduce:
1. Configure a host in ssh to be reacheable directly, authenticate with an id_rsa.
2. Configure another host with a login different from your current (configured with "User") to be reached via the above configured host (configured with "ProxyCommand ssh -W...".
3. Access this host using only an IdentityFile authentication with kio_fish.

Actual Results:  
kio_fish tries to connect to the "hidden host" with your current username and not the one configured in the .ss/config. Therefore the login fails and another username and password are asked for.

Expected Results:  
kio_fish should simply transparently connect to the "hidden host" just like the console ssh command.