You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Adding SSH keys of type ed25519 over the web interface as well as via dustbuilder service does not allow SSH access, resulting in a fallback to password authentication.
How to Reproduce
Steps to reproduce the behavior:
Add a ssh-ed25519 public key via the web interface or via dustbuilder service
Try to connect via ssh with ssh -i $ssh_key_in_ed25519_format root@roborock
SSH client falls back to password authentication
Expected behavior
SSH ed25519 keys are accepted by the Dropbear SSH server.
Vacuum Model: Roborock S5
Valetudo Version: RE 0.9.4
User-Agent irrelevant
Additional context
Dropbear got support for ed25519 keys with this Pull Request: mkj/dropbear#91
It's not included in an official release yet afaik, but this might be worth to look into in the future.
See also this comment by tripplet: #151 (comment)_
The text was updated successfully, but these errors were encountered:
Dropbear is definitely not a part of Valetudo application, and this is not an image builder repository.
I use vacuumz image builder for creating pre-built images, so that is better place to ask.
Describe the bug
Adding SSH keys of type ed25519 over the web interface as well as via dustbuilder service does not allow SSH access, resulting in a fallback to password authentication.
How to Reproduce
Steps to reproduce the behavior:
ssh -i $ssh_key_in_ed25519_format root@roborock
Expected behavior
SSH ed25519 keys are accepted by the Dropbear SSH server.
Vacuum Model: Roborock S5
Valetudo Version: RE 0.9.4
User-Agent irrelevant
Additional context
Dropbear got support for ed25519 keys with this Pull Request: mkj/dropbear#91
It's not included in an official release yet afaik, but this might be worth to look into in the future.
See also this comment by tripplet: #151 (comment)_
The text was updated successfully, but these errors were encountered: