connecting to remote host with ssh freezes when unexpected warning [$50]

[thomas parquier]

Files does not forward warning to user when ssh connection is blocked by a prompt, such as :

Warning: the ECDSA host key for 'vm.local' differs from the key for the IP address 'XX.XX.XX.XX'
Offending key for IP in /home/tom/.ssh/known_hosts:13
Are you sure you want to continue connecting (yes/no)?

[Cody Garver (codygarver)]

Bounty: https://www.bountysource.com/issues/1400695-connecting-to-remote-host-with-ssh-freezes-when-unexpected-warning

[Sergey "Shnatsel" Davidoff (shnatsel)]

Such things should be resolved manually, and people using SSH and running into a potential MitM are assumed to know what they're doing. So I believe Files should just explain what happened and abort.

So we need make the SSH process not hang and, ideally, to get the error message from the SSH. Making it not hang should be easy: just set the "StrictHostKeyChecking" option to "yes" instead of "ask", and it will exit with an error message instead of prompting the user.
Setting the options can be done either via the "-o" command-line argument or via config files. I haven't seen anything based on environment variables but that should not be required.

But this makes me wonder - does Pantheon Files actually contain its very own SSH handling code?! Shouldn't it use GVFS or something along those lines?

[The Lemon Man (lemonboy)]

Closed upstream by https://git.gnome.org/browse/gvfs/commit/?id=336fe869f06c8e792aa20170e6278b57c1c38c05

[Jeremy Wootten (jeremywootten)]

Confirmation is required as to whether this is still an issue in the latest version of Files (0.3.2).

[Launchpad Janitor (janitor)]

[Expired for Files because there has been no activity for 60 days.]