Arch Linux

Does the attached diff resolve the issue for you? It adds ssh-rsa to HostKeyAlgorithms in addition to ssh-dsa that it was previously adding.
If that does not work please try changing the patch to add ssha-rsa to PubkeyAcceptedAlgorithms.

Adding it to HostKeyAlgorithms is not enough, and for some reason sshfs doesn't accept a PubkeyAcceptedAlgorithms option:

> sshfs kdeconnect@192.168.1.31:/ /run/user/1000/******** -p 1745 -s -f -F /dev/null -o IdentityFile=/home/antonio/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=+ssh-rsa -o PubkeyAcceptedAlgorithms=+ssh-rsa -o uid=1000 -o gid=1000 -o reconnect -o ServerAliveInterval=30 -o password_stdin

fuse: unknown option(s): `-o PubkeyAcceptedAlgorithms=+ssh-rsa'

sshfs maintains its own list of ssh options[1], which does not contain PubkeyAcceptedAlgorithms, but does contain PubkeyAcceptedKeyTypes (equivalent to PubkeyAcceptedAlgorithms).

However, the existing is_ssh_opt function of sshfs is flawed and does not recognize PubkeyAcceptedKeyTypes as ssh parameters, so this parameter cannot be used.

Upstream sshfs issue: https://github.com/libfuse/sshfs/issues/237

[1]: https://github.com/libfuse/sshfs/blob/master/sshfs.c#L389

If sshfs is not patched, then the only workaround is to specify the ssh profile using -F and then use a configuration similar to the following.

ssh_config:
```
Host *
HostkeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa
```

Is the bug in sshfs where the options PubkeyAcceptedKeyTypes and PubkeyAuthentication are not accepted caused by a missing comma at the end of line 435 [1]?

[1] https://github.com/libfuse/sshfs/blob/master/sshfs.c#L435

Turns out the sshfs issue is just a silly typo https://github.com/libfuse/sshfs/pull/269

EDIT: loqs beat me by a second

I am not familiar with C, and I am glad you found the problem.

We may temporarily patch sshfs and kde connect as a solution.