https://bugs.kde.org/show_bug.cgi?id=477673
--- Comment #23 from MikeC <mike.cloa...@gmail.com> ---
The comment above is a current workaround to get kdeconnect to work, and uses
a wrapper script file (chmodded as executable) at /usr/local/bin/sshfs with
content:
#!/usr/bin/env bash
SSHFS_BIN="/usr/bin/sshfs"
if [[ "$1" =~ ^kdeconnect ]]; then
"$SSHFS_BIN" "$@" -o HostKeyAlgorithms=+ssh-rsa -o
PubkeyAcceptedKeyTypes=+ssh-rsa
else
"$SSHFS_BIN" "$@"
fi
And then unpair any existing connected android device, and re-pair it. With the
wrapper script replacing the direct call to sshfs, the key generated for the
pairing will be rsa, and this allows the current version of kdeconnect to work
with the filesystem on the android phone using the newly created rsa key pair.
Any key pairs created with recent versions of sshfs will not work with the
current version of kdeconnect unless the sshfs wrapper script is in place to
replace the call to sshfs but allowing obsolete ssh key types (rsa).
However this is not fully satisfactory, since rsa key use in ssh is now
deprecated, and using the up-to-date version of sshfs would normally not allow
the use of the rsa key pair. The correct solution would be that kdeconnect
works with the newer key types, and is compatible with the allowed keys in use
in the most recent version of sshfs (and ssh). This change needs to be put in
place with suitable commit for the kdeconnect source. So the real fix would be
to make sure that the key type when pairing will be compatible with up to date
versions of sshfs, and to have a warning if the ssh key is not permitted by
sshfs.
--
You are receiving this mail because:
You are watching all bug changes.
