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.20211208 released
Date: Wed, 08 Dec 2021 16:20:37 +0100	[thread overview]
Message-ID: <20211208152043.C5CF5C00446@smtp.kernel.org> (raw)

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

Hello,

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

== Changes ==

  * compat: account for latest c8s backports
  * compat: update for RHEL 8.5
  
  We now support RHEL 8.5 and C8S.
  
  * compat: account for grsecurity backports and changes
  * crypto: curve25519-x86_64: solve register constraints with reserved registers
  
  Better compatibility with recent grsecurity kernels.
  
  * netns: actually test for routing loops
  * main: rename 'mod_init' & 'mod_exit' functions to be module-specific
  * device: reset peer src endpoint when netns exits
  * receive: use ring buffer for incoming handshakes
  * receive: drop handshakes if queue lock is contended
  * ratelimiter: use kvcalloc() instead of kvzalloc()
  * compat: siphash: use _unaligned version by default
  
  Upstream commits from this merge:
  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cbd92e7d74314e10a90d12a8f18f6fc66be4fb16
  
  * compat: udp_tunnel: don't take reference to non-init namespace
  
  This is an old bug unearthed by the routing loop test case added in this
  cycle. It turns out that for kernels ≤3.16, interfaces weren't being deleted
  when namespaces exited, due to improper namespace handling for kernel sockets
  in the udp_tunnel backport.

This release contains commits from: Jason A. Donenfeld, Mathias Krause, Randy 
Dunlap, Peter Georg, Gustavo A. R. Silva, and Arnd Bergmann.

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.20211208.tar.xz
  SHA2-256: c0e607138a17daac656f508d8e63ea3737b5221fa5d9288191ddeb099f5a3b92

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

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAmGwzR0QHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrswXEACxL+6G+4gsFiUUlc/Z60QDYWXFVGJdlTIN
MTgypGU08JNyb1QlaKsc94R1aoV99rKyxS7luHvXr9d6EMF7O0j3SIFqUMD3c4fV
s2IZETCxe85qBdT6xSNhlf5QcuC+aBRXyruZ6WBUk5PvGUWn2/54ERV8UQxydRRu
PZNIvZpRpiHDqHBrCo+PaFsrxbhh3Kw2uDE/CntYILo2pJHhAwvSFpjxX+IzCcKO
/FFOQl99gWQT4ijEDscNz6KjQMLIM0mZ5vFjpjhfGIYLc1iXgVYdzCHKxqKmfUCP
ttYPbnrlnQrwwT63qCqJA7fncYGxVxFiZICdOnA4myr1w+0oCvR2h/FwRdtsEhYP
pwUJJeKugfZkqtNTy8lm5FfA/tfk06wn6WwUuyfXQHMJ9EMR/Uf44v9+qlOzg1cq
RcbXYpwTZ92zUMDCRX4sNvbaBwW01V/BiLtjijYh/UyNI0vvephk4e/+45bB71jd
6dfEREIiHzxNO6HZ16ZTAAj3pRn2YWpp5xYC+mqKIhkwML1g+3u7lP+f66Gql0rG
iX/ln3qqUNijJ3cUwpjgq3stejL6mCd87SvIo8G5j80wRbT1vDXQwpYQO+KxIRZP
NEi1HjWKVdg7zwBjAR0REwfIeqNFalQlfdxDPE2kmjSLFxHf0pvQUIpXgn+x+6TE
WzWDF0eboA==
=vx+c
-----END PGP SIGNATURE-----

                 reply	other threads:[~2021-12-08 15:20 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=20211208152043.C5CF5C00446@smtp.kernel.org \
    --to=jason@zx2c4.com \
    --cc=wireguard@lists.zx2c4.com \
    --subject='Re: [ANNOUNCE] wireguard-linux-compat v1.0.20211208 released' \
    /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

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