https://bugs.kde.org/show_bug.cgi?id=419897
mini_bomba <konrad.far...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |konrad.far...@gmail.com
--- Comment #37 from mini_bomba <konrad.far...@gmail.com> ---
I appear to be having the same issue on Arch.
Operating System: Arch Linux
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.8-zen1-1-zen (64-bit)
Graphics Platform: Wayland
openssh version: 9.8p1-1
sshfs version: 3.7.3-2
After I saw no useful information in the journal, I decided to strace
kdeconnectd to see what commands it executes and try running them myself in a
terminal for more information.
I found this command:
> sshfs kdeconnect@<device ip>:/ /run/user/1000/<random guid> -p <port> -s -f
> -F /dev/null "-o"
> "IdentityFile=/home/mini_bomba/.config/kdeconnect/privateKey.pem" "-o"
> "StrictHostKeyChecking=no" "-o" "UserKnownHostsFile=/dev/null" "-o"
> "HostKeyAlgorithms=+ssh-dss\\,ssh-rsa" "-o" "PubkeyAcceptedKeyTypes=+ssh-rsa"
> "-o" "uid=1000" "-o" "gid=1000" "-o" "reconnect" "-o"
> "ServerAliveInterval=30" "-o" "password_stdin"
Running that command in a terminal (with a modified, existing mountpoint path)
resulted in the following output:
> command-line line 0: Bad key types '+ssh-dss,ssh-rsa'.
> read: Connection reset by peer
As I did not recognize the ssh-dss key type, I removed it from the options and
tried running the command again, which resulted in the phone's file system
being successfully mounted.
I confirmed that the ssh-dss key type was the issue by removing the other key
type (ssh-rsa) instead, which resulted in a similar "Bad key types" error.
Based on this investigation I suspect that support for the ssh-dss key type
must've been removed or disabled in a recent ssh version, but doesn't appear
critical to the function of kdeconnect - it just needs to stop explicitly
requesting it.
--
You are receiving this mail because:
You are watching all bug changes.
