From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-linux-compat v1.0.20200729 released
Date: Wed, 29 Jul 2020 10:19:31 +0200 [thread overview]
Message-ID: <914341600569c84c@mail.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new version, v1.0.20200729, of the backported WireGuard kernel module for
3.10 <= Linux <= 5.5.y has been tagged in the git repository.
== Changes ==
* compat: rhel 8.3 beta removed nf_nat_core.h
* compat: ipv6_dst_lookup_flow was ported to rhel 7.9 beta
This compat tag adds support for RHEL 8.3 beta and RHEL 7.9 beta, in addition
to RHEL 8.2 and RHEL 7.8. It also marks the first time that
<https://www.wireguard.com/build-status/> is all green for all RHEL kernels.
After quite a bit of trickery, we've finally got the RHEL kernels building
automatically.
* compat: allow override of depmod basedir
When building in an environment with a different modules install path, it's
not possible to override the depmod basedir flag by setting the DEPMODBASEDIR
environment variable.
* compat: add missing headers for ip_tunnel_parse_protocol
This fixes compilation with some unusual configurations.
This release contains commits from: Jason A. Donenfeld and Ricardo Mendoza.
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.20200729.tar.xz
SHA2-256: 690c7d9e115e2ff27386811cb495c9784678f717c8d6fc4cc7469dce373f252e
A PGP signature of that file decompressed is available here:
https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-1.0.20200729.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-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl8hMPsQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4Drs22EADY8PNxh653h2kUrDaiSFyHWfQ+9fg4p/Kt
14hj7uxFBCsEzwZst9aG85+2gJjVoHE/O4Zytq4p2tVP8xl220jwaTgbBicwuqly
oh4z5aMdVbcFZHueE7u5D1N4dQvGvNdAorYwzSf01670zql/onGIwYBQr+Qe3E3d
RWbRl50cBA8MbUSo6m+LPwtDvU+aMc8b+UK1P0yy/SeFifr8ULmIEAcFR+VLytSz
WRoESTOHnu3o6mboR/V5uhQzIay9AlYkuJsLBczGw+O4AMwKBsRW5u30VjAeE5TT
DtDdjJnUh/GN7CXvpftyCZhcsK1vRLPsEDz0MGb+XB3gA/eKws5nUbj5aQszh9bK
m3vB8kFEUlJpnrrUAnJNifJmeslEfTlLHjzkn5Lz1BwG3H3piSFvc5wyYmM9H+1k
bIvKOrnuU1d70MggJxhJ7DNpdSounGEu3uk5ONHzKsfIe+OASwsAn5gdGeM9OdzK
MxwBjXik0LO3pQUkV1mc6KiVvv6Dp0oIldlSwSkXWjQAkN39l7KhHrYJE7XkC6d0
9tqUHfBSi8z5nGAdTbiS3Do+WlgB/73Vzh9qia/Vzl90eXptq57BizqsbTGFzjpr
LUGC/2wFtry/lRlzHgDXeN0ToA+Zha4u/DPSGvh5U8VtkupzkQbfpmGb4D+YXoDk
Ey7maHbo5Q==
=AoZB
-----END PGP SIGNATURE-----
reply other threads:[~2020-07-29 8:19 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=914341600569c84c@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).