From: "Eric Light" <eric@ericlight.com>
To: wireguard@lists.zx2c4.com
Subject: Re: [ANNOUNCE] WireGuard 1.0.0 for Linux 5.6 Released
Date: Mon, 30 Mar 2020 15:20:15 +1300 [thread overview]
Message-ID: <7a0b9f59-0f17-4f7a-a174-272955706b2e@www.fastmail.com> (raw)
In-Reply-To: <CAHmME9qOpDeraWo5rM31EWQW574KEduRBTL-+0A2ZyqBNDeYkg@mail.gmail.com>
Oh, Jason, that is outstanding news! Congratulations to you and the whole team of people who have contributed - be it developing, blog posts, or financially.
Well done, you lot!
E
--------------------------------------------
Q: Why is this email five sentences or less?
A: http://five.sentenc.es
On Mon, 30 Mar 2020, at 15:16, Jason A. Donenfeld wrote:
> Hi folks,
>
> Earlier this evening, Linus released [1] Linus 5.6, which contains our
> first release of WireGuard. This is quite exciting. It means that
> kernels from here on out will have WireGuard built-in by default. And
> for those of you who were scared away prior by the "dOnT uSe tHiS
> k0de!!1!" warnings everywhere, you now have something more stable to
> work with.
>
> The last several weeks of 5.6 development and stabilization have been
> exciting, with our codebase undergoing a quick security audit [3], and
> some real headway in terms of getting into distributions.
>
> We'll also continue to maintain our wireguard-linux-compat [2]
> backports repo for older kernels. On the backports front, WireGuard
> was backported to Ubuntu 20.04 (via wireguard-linux-compat) [4] and
> Debian Buster (via a real backport to 5.5.y) [5]. I'm also maintaining
> real backports, not via the compat layer, to 5.4.y [6] and 5.5.y [7],
> and we'll see where those wind up; 5.4.y is an LTS release.
>
> Meanwhile, the usual up-to-date distributions like Arch, Gentoo, and
> Fedora 32 will be getting WireGuard automatically by virtue of having
> 5.6, and I expect these to increase in number over time.
>
> Enjoy!
> Jason
>
>
> [1]
> https://lore.kernel.org/lkml/CAHk-=wi9ZT7Stg-uSpX0UWQzam6OP9Jzz6Xu1CkYu1cicpD5OA@mail.gmail.com/
> [2] https://git.zx2c4.com/wireguard-linux-compat/
> [3]
> https://lore.kernel.org/netdev/20200319003047.113501-1-Jason@zx2c4.com/
> [4]
> https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/debian/dkms-versions?h=master-next
> [5]
> https://salsa.debian.org/kernel-team/linux/-/tree/master/debian%2Fpatches%2Ffeatures%2Fall%2Fwireguard
> [6] https://git.zx2c4.com/wireguard-linux/log/?h=backport-5.4.y
> [7] https://git.zx2c4.com/wireguard-linux/log/?h=backport-5.5.y
>
next prev parent reply other threads:[~2020-03-30 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 2:16 [ANNOUNCE] WireGuard 1.0.0 for Linux 5.6 Released Jason A. Donenfeld
2020-03-30 2:20 ` Eric Light [this message]
2020-03-30 5:13 ` Muenz, Michael
2020-03-30 12:24 ` Fredrik Strömberg
2020-03-30 13:17 ` Greg KH
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=7a0b9f59-0f17-4f7a-a174-272955706b2e@www.fastmail.com \
--to=eric@ericlight.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.