All of lore.kernel.org
 help / color / mirror / Atom feed
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:55:38 +0100	[thread overview]
Message-ID: <fa4b08be3b6fee08@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: 
  BLAKE2b-256: 

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

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl3o4hYQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrrDBEADQmcpc3SnrfeULKtV3IBeFti9t2H5GejG2
t8/9ekTEAEVRvKIklrltoFZ5gof02BPPuLC0zB0N9UbtRxWdedgYDRjlXPvrkMZd
lvdul+AEOsrj8yySNCNnBWDrUZ8njxWLAMQW4zJI0681yXbjm7ZV6gazeQ89bPei
cYpfgoAlHyVSyT+XeGWtiVoUbGZtK1ocj04bcEAfsF3DFRLKSADR9VzXOId5zNXQ
LMN3vJ0ZGXQey6hDOdbJ1JzwChSDYZGNYE1xtrNLIgx3uZgiNSfjKmPY9XUEc669
NIJc0TBcSlF8HODfUyeMEGhqoLoTz3bZp4ld6jN+5pJ35bd6lDktZM2sbclBTQOm
XeapJ2A5M1hfk74xRMdoZbQpA39idLbUp4INDqYLW+o0lZRRQocEUNw/4uDR0GA9
zOo4nfrMRz4shTgVTbW1So8O+N3aGqQ8n1P7FLHs3CmZmQut37fdIBJkhVSFnBmA
00xNdHYl5JplAWiF4qfKsly+wGGgBeKnWHTunJZ82j8lfqtPL+h5av82Qe1gpDBA
A/MoxyCWH5HedSqBYTNr+xVKuoIBITypCqjyuXlaOaOwSa0T0SjgP2ZjPbYliGZB
xjcgMaWZUKay0pGl1HjpADJ7Bk4llrCHegPFQ13fS3EibzE/BU79zsWT7mqjvJFT
/CK+hrQwRw==
=S8Aq
-----END PGP SIGNATURE-----
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2019-12-05 10:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 10:55 Jason A. Donenfeld [this message]
2019-12-06 15:10 ` [ANNOUNCE] WireGuard Snapshot `0.0.20191205` Available Jordan Glover
2019-12-06 15:20   ` Jason A. Donenfeld
2019-12-06 15:36     ` Jordan Glover
2019-12-06 15:52       ` Jason A. Donenfeld
2019-12-06 16:23         ` Jordan Glover
2019-12-06 17:35           ` Jason A. Donenfeld
2019-12-11 19:13             ` Jordan Glover
2019-12-11 19:22               ` Jason A. Donenfeld
  -- strict thread matches above, loose matches on Subject: below --
2019-12-05 10:57 Jason A. Donenfeld

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=fa4b08be3b6fee08@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.