problem w/ dropbear ssh

[Erik Hovland]

I am experiencing a problem when trying to use ssh to log into remote
hosts.

My setup:
h5550
familiar 0.8
opie 1.1.7

When I type 'ssh <username>@<hostname>', it fails with:
ssh: connection to <username>@<hostname>:22 exited: bad buf_getwriteptr

I tried installing dropbear 0.44 from the unstable feed but it produced
exactly the same failure. I am currently installing openssh...It works.

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.

E
--
Erik Hovland
mail: erik AT hovland DOT org
web: http://hovland.org/
PGP/GPG public key available on request
_______________________________________________
The Familiar Linux Distribution
Familiar mailing list
***@handhelds.org
https://handhelds.org/mailman/listinfo/familiar
irc://irc.freenode.net #familiar

[Phil Blundell]

Post by Erik Hovland
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?

p.


_______________________________________________
The Familiar Linux Distribution
Familiar mailing list
***@handhelds.org
https://handhelds.org/mailman/listinfo/familiar
irc://irc.freenode.net #familiar

[Erik Hovland]

Post by Phil Blundell

Post by Erik Hovland
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

[Matt Johnston]

Post by Erik Hovland
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%.

Yep, that patch looks fairly sane, I think the 2000 bytes
was somewhat arbitrary. The proper solution might be to set
the size at runtime rather than a fixed value - I'll look at
that for the next release.

Cheers,
Matt

Post by Erik Hovland
--- 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_ */

_______________________________________________
The Familiar Linux Distribution
Familiar mailing list
***@handhelds.org
https://handhelds.org/mailman/listinfo/familiar
irc://irc.freenode.net #familiar