From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sshd problem on WS2008R2 64bit
Date: Thu, 07 Mar 2019 08:54:00 -0000 [thread overview]
Message-ID: <20190307085358.GE3785@calimero.vinschen.de> (raw)
In-Reply-To: <8f23c838-5af5-bd4b-ca86-e41af530db17@SystematicSw.ab.ca>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
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...
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-07 8:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 1:03 Stephen Carrier
2019-03-06 12:12 ` Corinna Vinschen
2019-03-06 12:48 ` Corinna Vinschen
2019-03-06 14:17 ` Corinna Vinschen
2019-03-06 14:34 ` Corinna Vinschen
2019-03-06 15:30 ` Bill Stewart
2019-03-06 15:34 ` Corinna Vinschen
2019-03-06 15:59 ` Bill Stewart
2019-03-06 16:45 ` Bill Stewart
2019-03-06 20:13 ` Corinna Vinschen
2019-03-06 20:48 ` Bill Stewart
2019-03-06 20:59 ` Corinna Vinschen
2019-03-06 21:25 ` Bill Stewart
2019-03-06 23:44 ` Stephen Paul Carrier
2019-03-06 23:54 ` Stephen Paul Carrier
2019-03-07 6:15 ` Brian Inglis
2019-03-07 8:54 ` Corinna Vinschen [this message]
2019-03-07 14:04 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190307085358.GE3785@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).