https://bugs.kde.org/show_bug.cgi?id=400178

--- Comment #52 from Andras <andrasszerencs...@gmail.com> ---
(In reply to NiO from comment #50)
Nice, I'm glad it seems to be solved, thanks for the hard work!
I noticed something tough and I hope not but if this issue remains somehow then
may I highlight these two line from result above?:
---
kdeconnect.plugin.sftp: Starting process:  "sshfs kdeconnect@192.168.1.90:/
/run/user/1000/6745be67c0caf8bb -p 1739 -s -f -F /dev/null -o
IdentityFile=/home/adam/.config/kdeconnect/privateKey.pem -o
StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
HostKeyAlgorithms=+ssh-dss -o uid=1000 -o gid=1000 -o reconnect -o
ServerAliveInterval=30 -o password_stdin"
--
kdeconnect.plugin.sftp: stdout: "Warning: Permanently added
'[192.168.1.90]:1739' (RSA) to the list of known hosts.\r\n"
---
Technically speaking I know nothing about networking in deep but isn't
KDEConnect asks for ssh-dss type algorithm and by the end the system try to
give ssh-rsa?  I mean is it possible it's something with cryptographic
algorithms compatibility that the system in KDE neon won't provide the legacy
one?
Related to this, once I got this line for example:
---
kdeconnect.plugin.sftp: stdout: "Unable to negotiate with 192.168.0.0 port
1739: no matching host key type found. Their offer: ssh-rsa\r\n"
---
It's a long shot and maybe I'm speaking about nonsense but just in case I ask.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to