Displaying 3 results from an estimated 3 matches for "buffer_get_bignum_ret".
2016 Aug 02
2
Configure option '--with-ssh1' breaks openssh-7.3p1
...ersion string SSH-2.0-OpenSSH_7.3
ssh_exchange_identification: read: Connection reset by peer
/var/log/messages:
Aug 2 17:35:07 host102 sshd[7449]: Server listening on 0.0.0.0 port 222.
Aug 2 17:35:07 host102 sshd[7449]: Server listening on :: port 222.
Aug 2 17:36:03 host102 sshd[7455]: error: buffer_get_bignum_ret: \n
incomplete message
Aug 2 17:36:03 host102 sshd[7455]: fatal: buffer_get_bignum: buffer \n
error
The code after line 1111 in sshd.c (buffer_get_bignum) seems to be not
adequate any more.
I suppose the error will also show up on Centos.
Best regards
Rainer
2016 Aug 03
2
Configure option '--with-ssh1' breaks openssh-7.3p1
...case I'm surprised it starts at
> all. Exactly how are you starting sshd?
>
>> Aug 2 17:35:07 host102 sshd[7449]: Server listening on 0.0.0.0 port 222.
>> Aug 2 17:35:07 host102 sshd[7449]: Server listening on :: port 222.
>> Aug 2 17:36:03 host102 sshd[7455]: error: buffer_get_bignum_ret: \n
>> incomplete message
>
> that might be the newline confusing the re-exec protocol although I'm not sure.
>
> Please including complete debug logs for both client and server.
>
The newlines are *not* in the real calls, but are all inserted by me
into the email to indi...
2016 Aug 03
2
Configure option '--with-ssh1' breaks openssh-7.3p1
...entering fd = 8 config len 285
debug3: ssh_msg_send: type 0
debug3: send_rexec_state: done
debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8
-------------- next part --------------
Aug 3 03:31:56 host102 sshd[7449]: Received signal 15; terminating.
Aug 3 04:03:19 host102 sshd[8897]: error: buffer_get_bignum_ret: incomplete message
Aug 3 04:03:19 host102 sshd[8897]: fatal: buffer_get_bignum: buffer error
-------------- next part --------------
diff ../openssh-7.3p1.nossh1/config.h config.h
1722c1722
< /* #undef WITH_SSH1 */
---
> #define WITH_SSH1 1