Bug 448768

Summary:	SFTP Authentication failed
Product:	[Frameworks and Libraries] kio-extras	Reporter:	Zeno Endemann <zeno.endemann>
Component:	SFTP	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	bugs.kde.org, linus.kardell, sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Zeno Endemann 2022-01-19 13:01:28 UTC

SUMMARY

This bug bothered me for quite some time now. For some reason I cannot connect to my laptop via SFTP (and have to use fish as a fallback):
- `kioclient5 ls sftp://mylaptop` -> `kioclient5: Authentication failed.`
- `sftp mylaptop` -> works
- `kioclient5 ls fish://mylaptop` -> works

On my laptop sshd logs two lines when trying to connect: "Received disconnect from <ip, port>: Bye Bye [preauth]" and "Disconnected from authenticating user <username> <ip, port> [preauth]"

With other SFTP connections besides my laptop it does work as expected, but on the other hand I have a standard sshd setup on my laptop. The only real difference I can see is that my laptop is in a local network, all other SFTP connections I tried are online (so this might possibly be a race? - admittedly very wild conjecture). Anyway, any ideas what else I could try out or check? Thanks

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

Comment 1 Linus Kardell 2022-02-07 14:29:32 UTC

I'm also having this problem when connecting to some computers with the sftp kioslave on openSUSE Tumbleweed. For one of them, I had two identity files mapped in the ssh config, and sftp:// would only try the first one. Oddly, it still only tries the first one, even if I remove it from the SSH config, so I guess it caches it somewhere. For another one, sftp:// tries a whole bunch of different keys set for that host (but mapped to the same HostName with a different Port).

Comment 2 Harald Sitter 2022-03-07 14:18:15 UTC

Please file at https://www.libssh.org/ config parsing is done inside the library.

Comment 3 Zeno Endemann 2022-03-07 15:10:31 UTC

(In reply to Harald Sitter from comment #2)
> Please file at https://www.libssh.org/ config parsing is done inside the
> library.

Why do you think this is a config parsing problem? The ssh config seems to be read fine when using fish (or when connecting to remote sftp servers), why would that fail just for my laptop config?
Also, is it common here to just close an issue because the root cause might be coming from a used library? I know this is open source, I'm not entitled for anyone here to fix my issue, but it does give the impression that bug reports are not welcome here.