wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] WireGuardNT, a high-performance WireGuard implementation for the Windows kernel
Date: Sat, 16 Oct 2021 23:08:52 -0600	[thread overview]
Message-ID: <CAHmME9rL7FT=fmrV-Vv7RgWd5dvoPo29tK8ctbhG7KddvLXZ7A@mail.gmail.com> (raw)
In-Reply-To: <YQgrCfqIL2SWfF6G@zx2c4.com>

Hi folks,

As described in August:

On Mon, Aug 2, 2021 at 11:28 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>   Phase 3) WireGuardNT is enabled, and wireguard-go/Wintun is removed from
>            the client. [Do note: as projects and codebases, both Wintun and
>            wireguard-go will continue to be maintained, as they have
>            applications and uses outside of our WireGuard client, and Wintun
>            has uses outside of WireGuard in general.]

After a considerable amount of testing and 11 releases, we are now in
phase 3, and the transition is complete. WireGuard for Windows v0.5 is
being released as we speak, and contains WireGuardNT 0.10.1, which is
now fully WHQL Certified and will run on all flavors of Windows

Thank you very much to everyone who helped test and stabilize this code.


      parent reply	other threads:[~2021-10-17  5:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 17:27 [ANNOUNCE] WireGuardNT, a high-performance WireGuard implementation for the Windows kernel Jason A. Donenfeld
2021-08-13 11:52 ` Jason A. Donenfeld
2021-08-13 15:58   ` Re[2]: " Hendrik Friedel
2021-08-13 16:09   ` Peter Whisker
2021-08-14 11:03   ` Phillip McMahon
2021-08-14 21:37   ` Morten Christensen
2021-08-16  8:15   ` nomad
2021-09-09 11:41   ` Jason A. Donenfeld
2021-09-12 21:06 ` Jason A. Donenfeld
2021-09-12 21:54   ` Jeffrey Walton
2021-09-18  0:27     ` Jason A. Donenfeld
2021-10-17  5:08 ` Jason A. Donenfeld [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHmME9rL7FT=fmrV-Vv7RgWd5dvoPo29tK8ctbhG7KddvLXZ7A@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=wireguard@lists.zx2c4.com \


* 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).