From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-linux-compat v1.0.20210124 released
Date: Sun, 24 Jan 2021 14:50:05 +0100 [thread overview]
Message-ID: <4c225ba6d6bf4420@lists.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new version, v1.0.20210124, of the backported WireGuard kernel module for
3.10 <= Linux <= 5.5.y has been tagged in the git repository.
== Changes ==
* compat: SYM_FUNC_* was backported to c8s
* compat: skb_mark_not_on_list was backported to 4.14
This release addresses two small compat issues, one in CentOS 8 Stream and the
other in the recently released 4.14.217.
This release contains commits from: Jason A. Donenfeld.
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.20210124.tar.xz
SHA2-256: dac6e68cd4c3db441499850dfa8a70706384a3295f37fda1b839a50b79faef54
A PGP signature of that file decompressed is available here:
https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-1.0.20210124.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-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAmANeuoQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DritSD/wJQJkW95fCKjpaN617s3IPTg+k5dyQ83hh
JAoCuPcbx50hO+75TFFaYseTNI6qkVZT5xejyoWFxZ2oJ8lprTZTklEknuC7Zaj9
o/KbRUGT1jML/Oup4BLz4AAIZT4RECCQ5E2j/vQJFRyMbSopZ5F8qRpr7Uf51Mpo
uc+ZLPaylCcJPPJ8txh9esNPt0/F6QLZ89AkaNR/DC6BThc9f/2AVbZi4KT4QkRb
CDJa9OI9cVroFP3GL+hpbFIdxghLmG2/kRNnnkcXPfyWqPzpUksEkyjbk8ERJZqC
h1YZk54heDQvWnhDItO4cPg6Bh5M8z3823GgD3jnBeg7hCKRiQEJtaFJA0mqrlz7
z/+aF6xbagMzGVSC9R8p1tzqjU/Ov0WQ+Sc/9WRi/NDoDg8LH3CS9a2ichdcdiWu
ztdJibopa7JJbCxjXjvFpxe7+qrLc8rIGtHNWRnri5zafP+L3KKhvr8kzFyvxXk+
sPrCF7svJXYGcqFVX6Vb1h4s11clgFqFazADu8TfZkfr17DZvg7spwShLozgckis
FNKlPYh8Gc3qcauF67IpHQeojlRccKsc14MqgOvQRYzSCk71Tjg4W04aSGt58R15
+L40wsXvo9MWisLGaTDGrtfElruLUnwz3FutLr3YjZubw7u5U8b45VmxMar3zadk
v88lB5NWOA==
=GYqc
-----END PGP SIGNATURE-----
reply other threads:[~2021-01-24 13:50 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=4c225ba6d6bf4420@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.