Open sixtyfive opened 9 years ago
On top of that, even if you relax your sshd's requirements, Connectbot silently fails when it's unable to negotiate a key exchange method, leaving you hanging as if it's still trying to connect, when in fact all is said and done at that point.
It might be nice to have a verbose mode, similar to ssh -v, which shows the phases of connection, KEX, etc.
Okay, well, there are three things we probably need to close this: Cipher: chacha20-poly1305@openssh.com KEX: curve25519-sha256@libssh.org Keys: ed25519
you could use DH group exchange as well.
On Fri, Apr 3, 2015 at 5:19 PM, Kenny Root notifications@github.com wrote:
Okay, well, there are three things we probably need to close this: Cipher: chacha20-poly1305@openssh.com http://blog.djm.net.au/2013/11/chacha20-and-poly1305-in-openssh.html KEX: curve25519-sha256@libssh.org https://git.libssh.org/projects/libssh.git/tree/doc/curve25519-sha256@libssh.org.txt Keys: ed25519 https://github.com/jedisct1/libsodium
— Reply to this email directly or view it on GitHub https://github.com/connectbot/connectbot/issues/54#issuecomment-89423184 .
I already wrote that in 2f4da82b29f41a2fbc9669ff4852a8160bb7a6a7
KEX fixed by #370 (keys also partially fixed by that for server-side keys)
I added ETM modes to the library with connectbot/sshlib#49
@kruton Awesome, thanks! Any chance for a release with this soon? :)
It would be cool if you could take a look at the ciphers and MACs mentioned in https://stribika.github.io/2015/01/04/secure-secure-shell.html. Not sure what connectbot currently "speaks", but at least chacha20-poly1305 and hmac-sha2-512-etm would be good to have!