From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-linux-compat v1.0.20200401 released
Date: Wed, 01 Apr 2020 13:11:15 -0600 [thread overview]
Message-ID: <38846280368266f8@frisell.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new version, v1.0.20200401, of the backported WireGuard kernel module for
3.10 <= Linux <= 5.5.y has been tagged in the git repository.
== Changes ==
* compat: queueing: skb_reset_redirect change has been backported to 5.[45]
* qemu: bump default kernel to 5.5.14
An upstream stable backport broke our compat layer, which this release
rectifies.
This release contains commits from: Jason A. Donenfeld and Christian Hesse.
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.20200401.tar.xz
SHA2-256: 7dfb4a8315e1d6ae406ff32d01c496175df558dd65968a19e5222d02c7cfb77a
A PGP signature of that file decompressed is available here:
https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-1.0.20200401.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-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl6E50wQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrkKyD/9I2vPCtJxtW3zdsbFo6hHMvHuJfUPsj361
NyOk2VfsKSWIPAkBWP5pUZIxOMqCpB/oyyybfNMBo4863r6shStvMMqGifZMZBBK
kfYZGiE8A+nv9P9QWyzeiB6RPFHfeSWuzldhSFdoV6XLTwi0eWvMuvFRsCy/9P27
O0xgKyFjk3K7y74USDR/6xJK/6tzwpa2UYLaSxvIrO03D+qxgK4KQiNR53Oz+Gic
byPF14X57ibGx7NxVquAAPK1IA89zfNgM9TW6MTNvxctnmzm7AJ6JFIcfBlqyUGA
lQNRxST5j8HOMQAOFNlrhxTfIQP5R/KphfX35s/xBZdLPXm3//1V5is+SVNXcScD
attsaiJq7BP6R23hA/R3uJYd9nmEqUPBiKZLiSWcgsmN+pUrwuT62mrG79MVwO2z
pgo8Fo76rIOL5XwJnmqjtKpUnFRoS1NR72fz3qp9ep0Zg7eIW14p9iYEsHKXyr7z
DhLJSEuKZixfmJatpZEPwUMZSDwACSHjG8kpdMSDIMu/xkL42U2/8o79S1OQyRMD
nMklhBiPdKxF2jOSX9jtHamOiOijRw2tJeF/LOcXqwsQYBKnaxswKJ1tqyrMrpQG
nB90ccerpwN6Rup7DIrv3FXLniv9exilJquugimpZkiBIaLXCDhjHzsochdHFLi2
4ugVM6Aw+g==
=0Zlp
-----END PGP SIGNATURE-----
reply other threads:[~2020-04-01 19:11 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=38846280368266f8@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).