Modify

Opened 3 years ago

Closed 3 years ago

#17523 closed defect (fixed)

SSH2_MSG_UNIMPLEMENTED disconnects with newest dropbear 2014.65

Reported by: anonymous Owned by: developers
Priority: normal Milestone:
Component: base system Version: Trunk
Keywords: Cc:

Description

I'm testing trunk CC r42153 which includes dropbear 2014.65. Since the upgrade from dropbear 2014.63 to .65 a couple of days ago, I've noticed disconnects with an SSH2_MSG_UNIMPLEMENTED error when using PuTTY 0.63 to connect to it.

I e-mailed dropbear's author who kindly provided an explanation for the error and a bugfix (which will be part of the upcoming 2014.66):

That's a bit of a problem, I guess 2014.66 will be coming shortly :\  
It isn't meant to close the connection after inactivity.  What happens is:
Dropbear sends a keepalive after 300 seconds
PuTTY replies with "request failure" as expected
Dropbear doesn't recognise the response and sends SSH2_MSG_UNIMPLEMENTED
PuTTY exits because of the SSH2_MSG_UNIMPLEMENTED
I've fixed it in
https://secure.ucc.asn.au/hg/dropbear/rev/f7f6c15b0ec3

Attachments (0)

Change History (11)

comment:1 Changed 3 years ago by jogo

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in r42162

comment:2 follow-up: Changed 3 years ago by mroek

  • Resolution fixed deleted
  • Status changed from closed to reopened

I'm still getting the same error.
I've done a full clean and update (and rebuild) of my tree, and the patch from r42162 is present in /package/network/services/dropbear/patches.

comment:3 in reply to: ↑ 2 Changed 3 years ago by jogo

Replying to mroek:

I'm still getting the same error.
I've done a full clean and update (and rebuild) of my tree, and the patch from r42162 is present in /package/network/services/dropbear/patches.

What ssh client and version are you using?

comment:4 follow-up: Changed 3 years ago by mroek

TeraTerm v4.83 (which is the latest).

comment:5 in reply to: ↑ 4 Changed 3 years ago by jogo

Replying to mroek:

TeraTerm v4.83 (which is the latest).

I can confirm that Tera Term still breaks, as it already breaks with the initial GLOBAL_REQUEST, not the (wrong) reply from the server that was breaking putty.

comment:6 follow-up: Changed 3 years ago by anonymous

mroek, perhaps you could submit a bug report to dropbear's author at:
https://matt.ucc.asn.au/dropbear/dropbear.html

comment:7 in reply to: ↑ 6 Changed 3 years ago by mroek

Replying to anonymous:

mroek, perhaps you could submit a bug report to dropbear's author at:
https://matt.ucc.asn.au/dropbear/dropbear.html

Yep, will do!

comment:8 Changed 3 years ago by anonymous

Same, it disconnects after around 5 minutes. Client is Bitvise SSH Client 6.00.

comment:9 Changed 3 years ago by mattjohnston

The patch https://secure.ucc.asn.au/hg/dropbear/rev/0bb16232e7c4 should sort this out.
"Make keepalive handling more robust, this should now match what OpenSSH does"

comment:10 Changed 3 years ago by jogo

Should be now really fixed by r42249, thanks for reporting and pointing to the upstream commits.

comment:11 Changed 3 years ago by jogo

  • Resolution set to fixed
  • Status changed from reopened to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.