From: Chris Wagner <wagnerc@plebeian.com>
To: cygwin@cygwin.com
Subject: Re: Default mingw _WIN32_WINNT
Date: Mon, 11 May 2020 19:08:14 -0400 [thread overview]
Message-ID: <7661d7c84c44bdf5d8f40f0b3208e412@plebeian.com> (raw)
In-Reply-To: <00b7faf1141248605e8498c1d1a57e0b783b783e.camel@cygwin.com>
On 2020-05-11 12:53 pm, Yaakov Selkowitz wrote:
>> I would just like to chime in that it would be a crying shame if
>> Cygwin
>> were to ever drop support for Windows 7. There are many people,
>> myself
>> one, who are dead set against Windows 10.
>
> "Ever"?!? You do realize that, ESU aside, Windows 7 is out of support
> and therefore should be assumed to be vulnerable?
I suspect that something one day will make it untenable but Windows 7 is
no less secure or more vulnerable than it was a year ago. All software
should always be assumed to be always vulnerable. Is 10 secure on
patching day but then vulnerable until the next patch day? The number
of vulns in any software is fixed on the day it ships and it's whittled
down as patches come out. 7 has had a heck of a lot of security fixes.
It's new software that increases security holes. I have to use 10 at
work and it is a ghastly operating system.
Thanks.
next prev parent reply other threads:[~2020-05-11 23:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 21:42 Yaakov Selkowitz
2020-05-05 3:15 ` Biswapriyo Nath
2020-05-05 8:54 ` Corinna Vinschen
2020-05-05 9:05 ` Rainer Emrich
2020-05-05 10:06 ` JonY
2020-05-05 10:11 ` Corinna Vinschen
2020-05-11 14:55 ` Chris Wagner
2020-05-11 16:53 ` Yaakov Selkowitz
2020-05-11 23:08 ` Chris Wagner [this message]
2020-05-08 0:33 ` Yaakov Selkowitz
2020-05-08 9:29 ` Corinna Vinschen
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=7661d7c84c44bdf5d8f40f0b3208e412@plebeian.com \
--to=wagnerc@plebeian.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).