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 v0.0.20200205 released
Date: Wed, 05 Feb 2020 14:42:49 +0100	[thread overview]
Message-ID: <ff1abd785bd78c9e@frisell.zx2c4.com> (raw)

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

Hello,

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

Please note that until Linux 5.6 is released, this snapshot is a
snapshot rather than a secure final release.

== Changes ==

  * compat: support building for RHEL-8.2
  * compat: remove RHEL-7.6 workaround
  
  Bleeding edge RHEL users should be content now (which includes the actual
  RedHat employees I've been talking to about getting this into the RHEL kernel
  itself). Also, we remove old hacks for versions we no longer support anyway.
  
  * allowedips: remove previously added list item when OOM fail
  * noise: reject peers with low order public keys
  
  With this now being upstream, we benefit from increased fuzzing coverage of
  the code, uncovering these two bugs.
  
  * netns: ensure non-addition of peers with failed precomputation
  * netns: tie socket waiting to target pid
  
  An added test to our test suite for the above and a small fix for high-load CI
  scenarios.

This release contains commits from: Jason A. Donenfeld, Ilie Halip, and Eric 
Dumazet.

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 snapshot is available in compressed tarball form here:
  https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-0.0.20200205.tar.xz
  SHA2-256: 9669e165fc7252cab7f908ba57f160f6d57539b7cc81180f260cb675d2fd362b

A PGP signature of that file decompressed is available here:
  https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-0.0.20200205.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-----

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl46xksQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrgDRD/9ZMO1hpbyHjoguYN/NrdExxnWX3RoAHxry
yX5Dz3Pyl5WuFQ4dbvIW1PsZ4208sgx8/2wQ/F1tspmST32QwXiCyrLV1kJS30xK
CbtIcyX34rA+qu8hbtbGyRoEea/6Z8oMug+yoFydoZOKcnpcfR6dGkHvUy005c3R
mWq9ROva5kKJETU6D3ry+pGJv9ItfUnkIv/FJoPXx4cPF8K0bm2wzL0APOr/gGjt
IrvvHtUJ6r6QasiP6K2fMO9ihVczS7m9hVL4M7Bxx1X3lEmMRpwiMf2zInkoL9HV
b+FZzlFyNA+d7iRA/ZU40u9AxOwOwifbolm94aw8KI8dr9aKLmnusxIIAKsIYYa5
X7NeKdTJ3GsILMQGbNCESP44Tr4LgVM743m92P8MvHJZtDZAigPBrGS4mr/uASDi
XpU+dHqfL/Wehdk7UCaj2MJsgM42XzsSzGr6fAROP/Ck7JLaY83u17G6UbC26c30
Ktt1xPTL3FLJBnd23MMb3vlWNITytEVa7NoVN/i4Hv1+tFeUvSdzzE/+EvdlLotd
3c1gncM/TtbBUPa4o17IqF3vvzHQKsjQFl9BnvnusVEpNOBZRCadnqEr9sKQZ3Wa
X4H2LJaCtGMTrugQ/eF5wsaV+92aWNQ1s6fplNg/lwl9qX6mxAk118L2y8Aq0Oxd
O25DLiz/5A==
=fdbn
-----END PGP SIGNATURE-----
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

                 reply	other threads:[~2020-02-05 13:42 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=ff1abd785bd78c9e@frisell.zx2c4.com \
    --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).