[ANNOUNCE] WireGuard Snapshot `0.0.20191205` Available

From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] WireGuard Snapshot `0.0.20191205` Available
Date: Thu, 05 Dec 2019 11:57:51 +0100	[thread overview]
Message-ID: <fa4b08ea13cfe13a@frisell.zx2c4.com> (raw)

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

Hello,

A new snapshot, `0.0.20191205`, has been tagged in the git repository.

Please note that this snapshot is a snapshot rather than a final
release that is considered secure and bug-free. WireGuard is generally
thought to be fairly stable, and most likely will not crash your
computer (though it may).  However, as this is a snapshot, it comes
with no guarantees; it is not applicable for CVEs.

With all that said, if you'd like to test this snapshot out, there are a
few relevant changes.

== Changes ==

  * wg-quick: linux: suppress error when finding unused table

  This fixes a spurious warning messages seen with recent versions of iproute2
  and kernels.

  * wg-quick: linux: ensure postdown hooks execute
  * wg-quick: linux: have remove_iptables return true
  * wg-quick: linux: iptables-* -w is not widely supported

  Adding in iptables had some hiccups. For the record, I'm very unhappy about
  having to put any firewalling code into wg-quick(8). We'll of course need to
  support nftables too at some point if this continues. I'm investigating with
  upstream the possibility of adding a sysctl to patch the issue that iptables
  is handling now, so hopefully at somepoint down the line we'll be able to shed
  this dependency once again.

  * send: use kfree_skb_list
  * device: prepare skb_list_walk_safe for upstreaming
  * send: avoid touching skb->{next,prev} directly

  Suggestions from LKML.

  * ipc: make sure userspace communication frees wgdevice

  Free things properly on error paths.

This snapshot contains commits from: Jason A. Donenfeld.

As always, the source is available at https://git.zx2c4.com/WireGuard/ 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/snapshot/WireGuard-0.0.20191205.tar.xz
  SHA2-256: 4de4c0efa35f8eb170c27a0bc8977e5c0634b8e19c03915d03218cc88bb0adbe
  BLAKE2b-256: 3cf4f58e1e4982ea3f25f287ae035ac2cca86007ceeefd124003982bba800bd4

A PGP signature of that file decompressed is available here:
  https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20191205.tar.asc
  Signing key: AB9942E6D4A4CFC3412620A749FC7012A5DE03AE

If you're a snapshot package maintainer, please bump your package version. If
you're a user, the WireGuard team welcomes any and all feedback on this latest
snapshot.

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

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl3o4qoQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrgToEADabWFukMDvEvTES9ngUnco0xMEz0IOcagF
1GdRXdNugEuxLcpXZKPvqjG6NxehWP9dAygJvXoxGat6BTOKe7VzTqtr2yzSftxQ
Yxa5Fn1ZQGlBGfkKBkMy20QI5XJ43cZ9Rm69I5HybrBjaHa+l15F8soDzSs/Yo4H
LJPoilxi27kylDQDSTPlHRsuEOuwnxY2HRTHrDm13nGXys9eELSsZ0EF1y90kxYC
CV3St8BUCKRB8ezQQiIrTNuiLa9wvJvNAe0tCjUticQyhXlQF9J+vWxRJCr620D2
vAZ9+uPQj1vb9SyJZWhdm08Wc1zYAgty2POL+9x4Wmlz0pSGTbUJKAwNcvAeCBVL
21/72y8HEitK+5/qiTe9wqlNbWIMVqr0GmFod5eMheqfLaepOcCeVMuLhMIUpciD
1vsMzIfOJmNmHUqiDo+vpFVUvlX5NHyB60kn6d90kLgZmd8JqXItZ0qLYT2VIJUe
PKFCOl9p5MNRcYN5ORisOS0H9qkIOXuTaemwf94OvC0VsPxLe1m7dSvfAbHmpM0j
8qB1dWwCWpjy6zzZ0EatKRA5HBwDfWIt2VuhvUj1ai8ayPnXY6PPQsilj6v7OjMW
vvgX6q+NGJ423F5uCaxp/GY1d5ywLjAxURnXG4E3oEQ8RV5QspsvbXQDTV8Yu+0f
08e7E/G2Tg==
=Oi5b
-----END PGP SIGNATURE-----
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard