[Familiar] problem w/ dropbear ssh
Erik Hovland
erik at hovland.org
Fri Jan 14 05:10:00 WST 2005
On Wed, Jan 12, 2005 at 10:09:25PM +0000, Phil Blundell wrote:
> On Wed, 2005-01-12 at 13:53 -0800, Erik Hovland wrote:
> > Any advice? I am happy to use openssh. But its large size makes it
> > unattractive to others. Is there a way to provide dropbear for sshd and
> > openssh for ssh? It probably is more cumbersome for package maintainers
> > but more flexible for users.
>
> Yeah, this would just be a question of making the packages a bit more
> granular and using update-alternatives. There's also a third ssh client
> option available, namely putty.
>
> Of course, the best thing would be to fix the bug in Dropbear. I don't
> imagine this can be terribly difficult. Maybe someone would like to
> have a go at that?
Ok, I'll have a go. Patch attached. It seems ssh was barfing on the
2048-bit key the remote host was offering.
This fixed the problem for me. But I have no idea if there are
ramifications for increasing the kex buffer size by 50%.
E
--
Erik Hovland
mail: erik AT hovland DOT org
web: http://hovland.org/
PGP/GPG public key available on request
-------------- next part --------------
--- kex.h.orig 2005-01-13 12:39:26.081910000 -0800
+++ kex.h 2005-01-13 12:36:46.929681000 -0800
@@ -64,6 +64,6 @@
};
-#define MAX_KEXHASHBUF 2000
+#define MAX_KEXHASHBUF 3000
#endif /* _KEX_H_ */
More information about the Dropbear
mailing list