From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 34197 invoked by alias); 7 Mar 2019 14:04:35 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 34177 invoked by uid 89); 7 Mar 2019 14:04:34 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy= X-HELO: smtp-out-no.shaw.ca Received: from smtp-out-no.shaw.ca (HELO smtp-out-no.shaw.ca) (64.59.134.13) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 07 Mar 2019 14:04:32 +0000 Received: from [192.168.1.114] ([24.64.172.44]) by shaw.ca with ESMTP id 1tdNhTHRjgMsj1tdOhOZxL; Thu, 07 Mar 2019 07:04:30 -0700 Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: sshd problem on WS2008R2 64bit To: cygwin@cygwin.com References: <20190306124816.GR3785@calimero.vinschen.de> <20190306141716.GS3785@calimero.vinschen.de> <20190306143424.GU3785@calimero.vinschen.de> <20190306153404.GX3785@calimero.vinschen.de> <20190306201331.GB3785@calimero.vinschen.de> <20190306205931.GC3785@calimero.vinschen.de> <8f23c838-5af5-bd4b-ca86-e41af530db17@SystematicSw.ab.ca> <20190307085358.GE3785@calimero.vinschen.de> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <7fc41f4f-dae7-bb59-9be7-5b39bddbe836@SystematicSw.ab.ca> Date: Thu, 07 Mar 2019 14:04:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.2 MIME-Version: 1.0 In-Reply-To: <20190307085358.GE3785@calimero.vinschen.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00143.txt.bz2 On 2019-03-07 01:53, Corinna Vinschen wrote: > On Mar 6 23:15, Brian Inglis wrote: >> On 2019-03-06 13:59, Corinna Vinschen wrote: >>> I'm reasonably sure there won't be any fix for these systems for at >>> least two reasons: >>> - All affected systems are EOLed or in the last year of their Extended >>> Support Cycle, all ending on 2020-01-14. >>> - I opened a support case for an older Windows release a couple of years >>> ago. A fix for the problem has been refused because the problem was >>> fixed in the newer OS. I got told literally that the fix is to upgrade >>> to the newer OS. >> No backports on rolling releases reminds me of some other project? ;^p > Why, I can't imagine which project that could be... One that *doesn't have* design botches that can't be fixed by the maintenance team, but needs a redesign by the product team to fix in a later major release. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple