[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#513071: Regression: for some hosts etch can connect but lenny can't (password auth)

On Mon, 26 Jan 2009 11:42:22 +0000
Colin Watson <cjwatson@debian.org> wrote:

> On Mon, Jan 26, 2009 at 12:23:15AM -0500, Daniel Dickinson wrote:
> > Package: openssh-client
> > Version: 1:5.1p1-5
> > Severity: serious
> > Justification: regression from etch
> > 
> > 
> > I can connect to my router using ssh inside an etch chroot but
> > cannot connect using lenny's etch.
> The log is not very informative, unfortunately. Can you get any
> similar debugging log from the server to indicate why it reset the
> connection after SSH2_MSG_KEXDH_INIT?

Unfortunately no, it's the embedded firmware on the router/modem.  I
actually have a serial cable hooked up and have been able to log on but
the manufacturer has done evil things with the firmware that mean
dropbear isn't available as a command.  It is hidden inside a binary
that does the 'server' stuff on the router (and isn't even multicall by
name or called by command line; it's really locked down).  The router
doesn't log ssh to syslog, so there is nothing I can do.

Comtrend is evil.

> (From some preliminary web searches, I suspect that this may really
> be a dropbear bug for which we'll have to add some compatibility
> code. In that case I am not convinced that this really qualifies as
> serious.)
OTOH it works for etch, and it means embedded hardware using that
version of dropbear will be inaccessible in lenny (like my



And that's my crabbing done for the day.  Got it out of the way early, 
now I have the rest of the afternoon to sniff fragrant tea-roses or 
strangle cute bunnies or something.   -- Michael Devore
GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C      http://gnupg.org

Attachment: signature.asc
Description: PGP signature

Reply to: