From: Isaac Boukris <iboukris@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Should we sunset Windows 7 support?
Date: Tue, 10 Nov 2020 13:57:54 +0100 [thread overview]
Message-ID: <CAC-fF8Q8VV7Y1-xPfU7XAfAsGddANfuB8i1oC7uYP9MJQix6yg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9rW1e+rRc8q+-_eLR=U9OTn+Sn84ECJtGFY=Hjg8kzfEQ@mail.gmail.com>
Hello,
New to the list :)
On Tue, Nov 10, 2020 at 1:30 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hi,
>
> Windows 7 has been EOL'd by Microsoft since January of this year. It
> is no longer receiving security updates or fixes. This email is to get
> the conversation started about doing the same with WireGuard for
> Windows.
>
> Supporting Windows 7 is an ongoing maintenance burden. For example, we
> use SHA2 signatures instead of SHA1 signatures for our drivers, which
> is not something we want to compromise on, and as a result Windows 7
> users must have KB2921916 installed. But Microsoft never supplied
> KB2921916 via Windows Update and it removed all Windows 7 hotfixes
> from its webpage last year. So in order to keep supporting this, we're
> forced to add clunky disgusting code like this:
> https://git.zx2c4.com/wireguard-windows/commit/?id=b63957dc830e39c94844d2f0d32ba29575991e44
> Keen readers will wince at all the layering violations there. Do we
> really want to keep maintaining gross stuff like this? It makes me
> uncomfortable to have kludges like that sitting around in the code.
> Shouldn't I write an auto-downloader that then checks hashes?
> Shouldn't I build this into the installer? Shouldn't I.... waste tons
> of time supporting Windows 7 better?
>
> Probably not.
>
> But I know so many users are still using Windows 7. I'd like to hear
> from you to understand why, in order to assess when is the right
> moment to sunset our Windows 7 support.
I've had some experience in the past (~5 years ago) with VPN on ATMs,
and we had to support Windows XP at the time since the ATM software
didn't support anything else and was very slow to get updated (several
vendors).
Regards.
next prev parent reply other threads:[~2020-11-10 13:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 12:27 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
2020-11-10 12:57 ` Isaac Boukris [this message]
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=CAC-fF8Q8VV7Y1-xPfU7XAfAsGddANfuB8i1oC7uYP9MJQix6yg@mail.gmail.com \
--to=iboukris@gmail.com \
--cc=Jason@zx2c4.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).