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.20200623 released
Date: Tue, 23 Jun 2020 16:15:52 -0600	[thread overview]
Message-ID: <6cd7bfefd767fdf2@mail.zx2c4.com> (raw)

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

Hello,

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

== Changes ==

  * compat: drop centos 8.1 support as 8.2 is now out
  
  Of note, as well, is that we now have both RHEL7 and RHEL8 in our CI at
  <https://www.wireguard.com/build-status/>.
  
  * Kbuild: remove -fvisibility=hidden from cflags
  
  This fixes an issue when compiling wireguard as a module for ARM kernels in
  THUMB2 mode without the JUMP11 workaround.
  
  * noise: do not assign initiation time in if condition
  
  Style fix.
  
  * device: avoid circular netns references
  
  Fixes a circular reference issue with network namespaces.
  
  * netns: workaround bad 5.2.y backport
  
  This works around a back backport in the 5.2.y series.

This release contains commits from: Jason A. Donenfeld and Frank 
Werner-Krippendorf.

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.20200623.tar.xz
  SHA2-256: 130937724515799edf05ff8216bc837df8acda879428f3a7f96a3287758f9445

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

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl7yfwcQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrvxgEAC58ZDoAAyph0sVO5manhh+t4Gvai63+Wmf
Aoja8LyoforyHWrOH7FYfKIn2G1cRQDdiZ24Bg6DrPVfJRHKd2epA5ZuRVH6TqZ4
FfZCa7o1jx6Kmyh+3nNfL8GV+yiQdPcWcz7COw/NxHSp1bp2PmS5Sso6ArKrbaPE
1+AtaTCm7x8Jje5CAJvVIWqK8KO+ap8riF2gxgA7pIi67xF1rhQVQ6A977UYSyyn
UqVQf8xeQ+AWWM6x0fsUbwYsfza2ggR2lmpZad0CbP1Jx1/x+/YnFVMaRp709Ypg
bHigMC12LuetR5U35ldV1sKiVxWlovzxnoznjNzKvwx7HjO0vLT6IyuerhVRsIYQ
O+F0piRbMDKhz423SEij72ULvmyCrxnTxYU+ML9F/13HJFTJfYCtCr9bM6bSlEjt
wCzA+leFO7WErlE9Ut05qYAawJPVNFVGQhVHgTUfTo5CPV/3iKtmfVzA46QBiJJv
+GetUADVQjl96sV+eCnuGtY2bQv/nnUMJcg+U9lUtNSfBJyi+F/dc/c5ZrW99DqW
/rMvuJHxHIUITWI1IOCxCvi1hsKaV3kPLT1dNOUtsNHbhyj7ngQCSi7wjFiOH8BU
74oLNAjU6ooD2PAWJUiam6YDii1cmBKseYRlaljpDnfXZDAn66wZdFFhtYcRmxms
TjlXXorVHQ==
=s2+A
-----END PGP SIGNATURE-----

                 reply	other threads:[~2020-06-23 22:16 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=6cd7bfefd767fdf2@mail.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).