From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-linux-compat v0.0.20200214 released
Date: Fri, 14 Feb 2020 14:38:48 +0100 [thread overview]
Message-ID: <ff1bc7a55ddd0da2@frisell.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new version, v0.0.20200214, of the backported WireGuard kernel module for
3.10 <= Linux <= 5.5.y has been tagged in the git repository.
Please note that until Linux 5.6 is released, this snapshot is a
snapshot rather than a secure final release.
== Changes ==
* chacha20poly1305: defensively protect against large inputs
Defense-in-depth sort of check.
* netns: ensure that icmp src address is correct with nat
We finally upstreamed the last remaining compat.h hack in this patch series:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=803381f9f117493d6204d82445a530c834040fe6
That means we can port compat.h to use the new proper API.
* receive: reset last_under_load to zero
Matt found a small optimization while porting the Linux kernel module to
OpenBSD's kernel.
* send: account for mtu=0 devices
This fixes issues related to setting the MTU of a device to zero.
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 snapshot is available in compressed tarball form here:
https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-0.0.20200214.tar.xz
SHA2-256: 6aaed62beb23803a456b7875a56e9462125a589c9dfb6d0b672c1a8f9f3f45ab
A PGP signature of that file decompressed is available here:
https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-0.0.20200214.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-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl5GouAQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrjcREADZ62q40fW86qwDY2c3WglegysWlytKNuy2
fzyg07ZbJpoN4mUWzVxwv96ewkU4q34iwJ/EM5/LGqV+uP4rsLWO8HeaT/TdTsfi
OPSwnx5B89Hc8N+RejDB++eCtVU1nr6BEPIyK/Gi8Ng4biZWea5U7Q85/gAYOLVE
W5HN51XobxRa0W0Y7DYGpMONXXWRXh1YICtROUo51Z/l1SsR9/B8K/uKoXuqGJR7
GKVrjkdSQDJTQIIepkn123xL/2s4QncfSqpDkbxnQKAn1rh3ZlfFDUDsjfJVLFnP
4A+pfF2Z82vURZNgtV70Ur1w0niuIHUC7NMbQJEHaaapMa7CQZ1pkOJR549KGG1r
6PQ28USZf6ZLxY0dkHesuTzkbYlSxM1+Sodi3lqyEmJy/laavVzR62EP/k7d/i9g
UJkDS5yRs8yg4KXLtqUqYJEy62ZTS0CbmbSMFPgPlXYXtymzXec1f4QHE/h2n9Kt
MDH7O4vSxYnKAjj4tHpabIfK8f0Brl7Ha1WOJbYhG7sA9bgylGuMh5ruv8U/SHlY
V4v0/fM4PQxmHJxyzKaQ1BDj14a/zy4LcBogUtGqKJ0X2DQ/HBap154lPM0q5TT8
Ov026Uts4dqIm4lMk2qiC06WaAYhXFHsiunpmBtpOd+dzwHmDc6bMYCdkFRFFZt9
gkjz6SzcOQ==
=leGA
-----END PGP SIGNATURE-----
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2020-02-14 13:39 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=ff1bc7a55ddd0da2@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 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.