Why ssh client breaks connection in expecting SSH2_MSG_NEWKEYS state?

[Darren Tucker]

On Wed, Dec 11, 2013 at 10:17 PM, Yuri <yuri at rawbw.com> wrote:
> On 12/11/2013 02:09, Darren Tucker wrote:
>>
>> That's a modified ssh server.  Can you reproduce the problem with a
>> stock openssh from openssh.com?
>
> The modification is minor, to port for FreeBSD. It did work with this
> modification on the same system.

Please post the debug output from the stock openssh client and server.

>> You might get some more clues if you run the server in debug mode
>> (/path/to/sshd -ddde).
>
> Unfortunately, this didn't give any new clues. No new debug messages around
> the failure.
>
> I also looked at the server system call trace, and the first major
> difference is that in successful case one read(2) call returns 16 bytes, and
> in failed case it returns 0 bytes, which means disconnect.
>
> What are the possible client failure points between the server events
> 'expecting SSH2_MSG_NEWKEYS' and 'SSH2_MSG_NEWKEYS received'?

tough to say without seeing the server-side debug output.

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.