Test Failure OpenSSH 7.1 P2 on HPE NSE for integrity

Damien Miller djm at mindrot.org
Fri Feb 26 11:53:21 AEDT 2016


On Thu, 25 Feb 2016, Randall S. Becker wrote:

> > if the server never sends an "exit-status" packet (as opposed to an "exit-
> > signal" packet, which it does send) then the exit-status code in
> > client_input_channel_req() will never get called and exit_status will remain -1
> > since that's what it's initialized to.
>
> Status update:
>
> We have isolated this situation down to at sshd-log-wrapper.sh where
> the exec call is returning immediately and improperly after sshd is
> started. The output from sshd is never properly captured so we do
> not see the "Corrupted" messages in the logs. The team is currently
> suspecting that exec is being a bit wonky and are trying to reproduce
> this independently. I don't suppose there is a different way to
> implement this test that does not depend on exec?

The exec in sshd-log-wrapper.sh is just an optimisation to avoid keeping
an unnecessary shell around. You could just try removing it.

-d


More information about the openssh-unix-dev mailing list