From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: samuel.progin@gmail.com
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Should we sunset Windows 7 support?
Date: Tue, 10 Nov 2020 14:06:46 +0100 [thread overview]
Message-ID: <CAHmME9ohdWGA=B=70FHe6xRA03h8GZEzMT9hVZ+x_sRB11c0RQ@mail.gmail.com> (raw)
In-Reply-To: <00fa01d6b760$da95c480$8fc14d80$@gmail.com>
On Tue, Nov 10, 2020 at 2:05 PM <samuel.progin@gmail.com> wrote:
> FWIW, Microsoft sells extended support (Windows 7 ESU) to corporate
> customers using Pro or Enterprise editions. It can be extended until Jan
> 10th 2023.
>
> https://docs.microsoft.com/en-us/troubleshoot/windows-client/windows-7-eos-f
> aq/windows-7-extended-security-updates-faq
I thought about this... One thing I wonder is: are purchasers of ESU
the same group of people that are likely to run newfangled security
software like WireGuard? How likely is there to be an overlap? I
realize my question implies, "not very likely," but I really don't
know too much about who Microsoft sells this stuff to, so if you have
any insights, I'm all ears.
next prev parent reply other threads:[~2020-11-10 13:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 12:27 Should we sunset Windows 7 support? Jason A. Donenfeld
2020-11-10 12:47 ` Laslo Hunhold
2020-11-10 12:56 ` samuel.progin
2020-11-10 13:06 ` Jason A. Donenfeld [this message]
2020-11-10 12:57 ` Isaac Boukris
2020-11-10 15:06 ` Reiner Karlsberg
2020-11-12 8:34 ` Jason A. Donenfeld
2020-11-12 9:13 ` Roman Mamedov
2020-11-10 17:38 ` Andrew Fried
2020-11-12 8:38 ` Jason A. Donenfeld
2020-11-12 8:46 ` Phillip McMahon
2020-11-12 8:50 ` Jason A. Donenfeld
2020-11-12 9:03 ` Berge Schwebs Bjørlo
2020-11-13 2:56 ` Jeffrey Walton
2020-11-19 16:59 ` Jason A. Donenfeld
2020-11-19 17:16 ` akloster
2021-10-07 23:35 ` Jason A. Donenfeld
2020-11-12 21:56 ` Panagiotis Kalogiratos
2020-11-12 17:38 ` Jeffrey Walton
2020-11-12 17:42 ` Phillip McMahon
2020-11-12 18:11 ` Neal Gompa
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='CAHmME9ohdWGA=B=70FHe6xRA03h8GZEzMT9hVZ+x_sRB11c0RQ@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=samuel.progin@gmail.com \
--cc=wireguard@lists.zx2c4.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 NNTP newsgroup(s).