I've had a few reports of this but can't reproduce it, which
is awkward for debugging. Is there anything of note about the OS or
hardware that might help?

Dropbear is actually returning no exit status packet at all,
and the ssh client itself sets 255 (AFAICT). A successful
run is below ("client_input_channel_req exit-status" is the
exit-code that gets sent).

Matt
Dropbear developer


ssh -v somehost true
...
debug1: Remote protocol version 2.0, remote software version dropbear_0.50
...
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Requesting authentication agent forwarding.
debug1: Sending command: true
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.0 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 0
debug1: compress outgoing: raw data 1093, compressed 726, factor 0.66
debug1: compress incoming: raw data 433, compressed 431, factor 1.00


On Sun, Oct 28, 2007 at 03:34:00PM -0400, Joey Hess wrote:
> Package: dropbear
> Version: 0.50-2
> 
> dropbear seems to communicate a nonzero exit status to openssh-client
> when the command run returns true.
> 
> [EMAIL PROTECTED]:~>ssh slug true
> zsh: exit 255   ssh slug true
> 
> ssh -v shows:
> 
> debug1: Entering interactive session.
> debug1: Sending environment.
> debug1: Sending env LC_TIME = C
> debug1: Sending env LC_COLLATE = C
> debug1: Sending env LANG = en_US.UTF-8
> debug1: Sending command: true
> debug1: channel 0: free: client-session, nchannels 1
> debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.4 seconds
> debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
> debug1: Exit status -1
> debug1: compress outgoing: raw data 1237, compressed 681, factor 0.55
> debug1: compress incoming: raw data 518, compressed 552, factor 1.07
> zsh: exit 255   ssh -v slug true
> 
> This breaks scp to hosts running dropbear, since it thinks the scp command
> run on the dropbear host exits nonzero (even though it really succeeded).
> scp transfers a file ok, and then exits nonzero.
> 
> -- 
> see shy jo






-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to