Doesn't work with dropbear in arch or kali linux
See original GitHub issueUserLAnd sends ssh intents out for people to connect to their boxes which we create. We direct people to connectbot if they have no SSH app that supports such an intent installed yet. This has worked fairly well (except #599 and #619), but now we are adding more distributions that you can install in userland which has brought up a new issue. Both Arch and Kali linux use newer cyphers (I assume that is the issue) which connectbot does not support. We get the following error
Connection Lost
Key exchange was not finished, connection is closed.
Cannot negotiate, proposals do not match.
This works fine with JuiceSSH but we want to stick with connectbot since it is FOSS.
Any thoughts or any known workaround?
Issue Analytics
- State:
- Created 5 years ago
- Comments:31 (6 by maintainers)
Top Results From Across the Web
DropBear on Kali Linux Raspberry Pi SSH Error
I am trying to set up an encrypted Raspberry Pi running Kali with the capability of remote SSH in case it stalls/reboots/etc (as...
Read more >How to install and configure Dropbear on Linux
The dropbear suite provides both an ssh server and a client application (dbclient), and represents a light alternative to OpenSSH .
Read more >How to unlock LUKS using Dropbear SSH keys remotely in ...
Explains how to unlock LUKS encrypted disk using Dropbear SSH keys remotely in Linux when you don't have access to the KVM console....
Read more >[solved] dropbearconvert refuses all kinds of OpenSSH keys
But I ran into the problem that the initcpio dropbear installl hook was unable to automatically convert and use my openssh key(s). So...
Read more >r/termux - Cannot use ssh, tried installing openssh or dropbear ...
r/termux - Cannot use ssh, tried installing openssh or dropbear, got " ... r/VFIO - Win10 VM doesn't work (single GPU) ... r/Kalilinux...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If I simply copy the keys from kali into debian and restart the server and then try to connect via connectbot it does in fact fail. So you can try simply swapping the keys I have provided.
Yes, just copying the different ecdsa keys back and forth will make it so you get the “proposals do not match error shows up”
That gives me a pretty easy work around (I think). I can just have the startup script create keys of a certain size that is the same for all distros. But ideally it would be fixed in connectbot too.
My work around works fine, so I won’t harass you about this, but please to tell me when it is fixed. I mentioned a couple of more issues that matter to UserLAnd earlier and will watch to see if they are resolved as well.