On February 9, 2016 9:30 PM, Darren Tucker wrote: > To: Randall S. Becker <rsbecker@xxxxxxxxxxxxx> > Cc: OpenSSH Devel List <openssh-unix-dev@xxxxxxxxxxx> > Subject: Re: Test Failure OpenSSH 7.1 P2 on HPE NSE for integrity > [...] > This one looks odd. The ssh session itself looks OK: it authenticates then > sends a printf shell command (basically, just a way of guaranteeing a > minimum amount of output being sent back: > > > debug1: Sending command: printf "%4096s" " " > > The session then closes OK but ssh exists with a -1 error code, which gets > propagated back up the stack as a failure. > > > debug1: Exit status -1 > > Exit statuses in POSIX should be 0-255. We can see in the sshd.log that the > server sent an exit status (session_exit_message), so either your printf > command/builtin returns a bogus exit code, or ssh is mishandling it. > > What's the return code of printf? ie: > > printf "%4096s" " "; echo $? Dumps 4K of blanks. Exit code reports 0, as expected. Tried in bash and ksh. Is there a missing return buried that ssh is pulling a non-zero off the stack somewhere? _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
