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

Attachment: signature.asc
Description: Digital signature

Reply via email to