Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-linux-compat v1.0.20220627 released
Date: Mon, 27 Jun 2022 12:59:34 +0200	[thread overview]
Message-ID: <20220627105937.BCD68C3411D@smtp.kernel.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello,

A new version, v1.0.20220627, of the backported WireGuard kernel module for
3.10 <= Linux <= 5.5.y has been tagged in the git repository.

== Changes ==

  * compat: drop Ubuntu 14.04
  
  We announced it was going to be EOL a long time ago, and now it finally is.
  
  * qemu: give up on RHEL8 in CI
  
  RHEL8 makes CI impossible and their kernel team doesn't accept patches to fix
  it. So just drop it from CI. This means that likely CentOS 8 "Stream" support
  will falter. If you're interested in having RHEL8 support up to date, please
  get in touch.
  
  * crypto: curve25519-x86_64: use in/out register constraints more precisely
  * queueing: use CFI-safe ptr_ring cleanup function
  * qemu: simplify RNG seeding
  * socket: free skb in send6 when ipv6 is disabled
  * socket: ignore v6 endpoints when ipv6 is disabled
  * qemu: enable ACPI for SMP
  * device: check for metadata_dst with skb_valid_dst()
  * netns: make routing loop test non-fatal
  * netns: limit parallelism to $(nproc) tests at once
  * qemu: use vports on arm
  * qemu: set panic_on_warn=1 from cmdline
  
  Various fixes from upstream, now backported.
  
  * compat: handle backported rng and blake2s
  
  Recent kernels did large backports of the RNG code and BLAKE2s, which the
  compat layer previously had various stubs for. Now the compat layer uses the
  properly backported code instead.

This release contains commits from: Jason A. Donenfeld, Wang Hai, and Nikolay 
Aleksandrov.

As always, the source is available at https://git.zx2c4.com/wireguard-linux-compat/
and information about the project is available at https://www.wireguard.com/ .

This version is available in compressed tarball form here:
  https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-1.0.20220627.tar.xz
  SHA2-256: 362d412693c8fe82de00283435818d5c5def7f15e2433a07a9fe99d0518f63c0

A PGP signature of that file decompressed is available here:
  https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-1.0.20220627.tar.asc
  Signing key: AB9942E6D4A4CFC3412620A749FC7012A5DE03AE
  Remember to unxz the tarball before verifying the signature.

If you're a package maintainer, please bump your package version. If you're a
user, the WireGuard team welcomes any and all feedback on this latest version.

Finally, WireGuard development thrives on donations. By popular demand, we
have a webpage for this: https://www.wireguard.com/donations/

Thank you,
Jason Donenfeld


-----BEGIN PGP SIGNATURE-----

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAmK5jY0QHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DroByD/44LVUG2mmvrbBWFuJ30gXeT7P4m8uNJJwB
Ykup/HcA/CSaKvhCqIFE+Vc2BqY/Ns8Tp3qucVwZ6EF80w42AICFwD8S+c8X88er
9LSbGvXiW3Pjvs2oXtiDnhgNZt/msM7EtLODkH3SuVoTaYcsecG5K42k+IcKrteR
Du5XfN4nuMGV4CSYoTQlyId9VLigEasb3CfA6yTV3VA7Ry4V+LTeE/Ngy1S5FNxj
UENZ5sptzA7OEwdgkb7gHw00MrHW3ptd5UUEQAai1rVWRl4pHNq2HC1VMsdkTbQ0
nWXEZWNcZT2dJWzxrsbtvGAzEQ/UoTyzzjckpTk5xHE4GAuG0tEIhMoFaD+knqDQ
gornocfeOjyZD5Tk86MM4rmGkICW3YGpqoEQrxrhzuUwZfytf1cl5Deock8ODjNF
PGfMEWmibVfW+/RHwIi/6niH644mdUlBEU+ilXstBXDSVpf4QhKzQYdqdV8v9xVh
OulrmVRikX8tMQ0b2hHbC5yh7u0K0QRJGqnRl36OrYNhF2Ny/zKcp5ASjDCNFDW4
o8++eQzzMqzLknmmWyrG9aeQeVvx6gOmqozItUz0uV4CGegq9m2CdXhsQyySpkqk
tWCWOaDrYjHHdV2YHVT3JlcS8/CTLI1nMIY2D+T8RTIeHb6546OyBUNG/zwUliVh
cAdOuxrEag==
=Jp6L
-----END PGP SIGNATURE-----

                 reply	other threads:[~2022-06-27 10:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220627105937.BCD68C3411D@smtp.kernel.org \
    --to=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).