Displaying 3 results from an estimated 3 matches for "4096s".
Did you mean:
4096
2016 Feb 10
2
Test Failure OpenSSH 7.1 P2 on HPE NSE for integrity
...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 a...
2016 Feb 12
2
Test Failure OpenSSH 7.1 P2 on HPE NSE for integrity
...t;> > 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
>
> I put in a couple of debug statements in clientloop.c...
2016 Feb 09
2
Test Failure OpenSSH 7.1 P2 on HPE NSE for integrity
...2: channel 0: send open
debug1: Requesting no-more-sessions at openssh.com
debug1: Entering interactive session.
debug1: client_input_global_request: rtype hostkeys-00 at openssh.com
want_reply 0
debug2: callback start
debug2: client_session2_setup: id 0
debug1: Sending command: printf "%4096s" " "
debug2: channel 0: request exec confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_status_confirm: type 99 id 0
debug2: exec request accepted on channel 0
debug2: channel 0: rcv...