Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: 15 Nov 2001 17:41:41 -0500 Message-ID: <20011115224141.7678.qmail@lizard.curl.com> From: Jonathan Kamens To: cygwin-developers AT cygwin DOT com CC: cygwin-developers AT cygwin DOT com In-reply-to: <20011115233753.E27452@cygbert.vinschen.de> (message from Corinna Vinschen on Thu, 15 Nov 2001 23:37:53 +0100) Subject: Re: Fixing openssh to avoid occasional spurious connection failures References: <20011115213959 DOT 6226 DOT qmail AT lizard DOT curl DOT com> <052f01c16e1f$ffb61890$0200a8c0 AT lifelesswks> <20011115215733 DOT 6471 DOT qmail AT lizard DOT curl DOT com> <20011115230625 DOT D27452 AT cygbert DOT vinschen DOT de> <20011115221455 DOT 6571 DOT qmail AT lizard DOT curl DOT com> <20011115233753 DOT E27452 AT cygbert DOT vinschen DOT de> > Date: Thu, 15 Nov 2001 23:37:53 +0100 > From: Corinna Vinschen > > Can you give me a pointer to the KB article describing that > winsock bug? If there were a KB article about it, my life would have been a lot easier :-). I couldn't find any evidence in the KB that Microsoft knows about this bug (or, at least, that they acknowledge publicly that they know about it). Like I said in my previous E-mail, I'm going to have our guy with the MSDN subscription file a support request about the problem, but he's going to wait until after Thanksgiving to do it (since he's going on vacation next week and it's not good to file a support request and then not return their calls about it). I'll keep you posted if/when we hear something definitive from M$ about it. jik