Re: Client fails kex after c38ea634893a1975dbbec798fb968c9488013f4a

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

To: Darren Tucker <dtucker@xxxxxxxxxx>
Subject: Re: Client fails kex after c38ea634893a1975dbbec798fb968c9488013f4a
From: Neale Ferguson <neale@xxxxxxxxxxxxxx>
Date: Fri, 20 Jan 2017 15:35:05 +0000
Accept-language: en-US
Cc: "openssh-unix-dev@xxxxxxxxxxx" <openssh-unix-dev@xxxxxxxxxxx>
In-reply-to: <CALDDTe2vYHcZ7AambzXj-PiyReBt_VFmCmPt=BMAdEo0dg+e6w@mail.gmail.com>
References: <D4A64A48.858D2%neale@sinenomine.net> <CALDDTe0rY9f+AP_n57CWktg7aw-q8xz6C_qLbHxpSqvvGfffng@mail.gmail.com> <CALDDTe2vYHcZ7AambzXj-PiyReBt_VFmCmPt=BMAdEo0dg+e6w@mail.gmail.com>
User-agent: Microsoft-MacOutlook/14.7.1.161129

I found the problem. I was scanning for CRLF in the version string coming
back from SSHD. It changed to just a CR. 

_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@xxxxxxxxxxx
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

References:
- Client fails kex after c38ea634893a1975dbbec798fb968c9488013f4a
  - From: Neale Ferguson
- Re: Client fails kex after c38ea634893a1975dbbec798fb968c9488013f4a
  - From: Darren Tucker
- Re: Client fails kex after c38ea634893a1975dbbec798fb968c9488013f4a
  - From: Darren Tucker

Prev by Date: Re: ^C doesnt work on ssh session
Next by Date: Open SSH public key setup not working on windows 2012
Previous by thread: Re: Client fails kex after c38ea634893a1975dbbec798fb968c9488013f4a
Next by thread: Re: Client fails kex after c38ea634893a1975dbbec798fb968c9488013f4a
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]

Powered by Linux