connectbot: Doesn't work with dropbear in arch or kali linux
UserLAnd 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?
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 31 (6 by maintainers)
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.