From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [WireGuard] [ANNOUNCE] Snapshot `experimental-0.0.20161014` Available
Date: Fri, 14 Oct 2016 18:06:31 +0200 [thread overview]
Message-ID: <ffffffffd626322a@frisell.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new experimental snapshot, `experimental-0.0.20161014`, has been tagged in
the git repository.
Please note that this snapshot is, like the rest of the project at this point
in time, experimental, and does not consitute a real release that would be
considered secure and bug-free. However, if you'd like to test this snapshot
out, there are a few relevent changes.
== Changes ==
* send: only avoid parallel path when there aren't inflight jobs
* send: requeue jobs for later if padata is full
* send: ensure that rekey retries are staggered
* device: show debug message when no peer has allowed-ips for packet
* compat: more functions moved upstream into 4.9
As always, the source is available at https://git.zx2c4.com/WireGuard/ and
information about the project is available at https://www.wireguard.io/ .
This snapshot is available in tarball form here:
https://git.zx2c4.com/WireGuard/snapshot/WireGuard-experimental-0.0.20161014.tar.xz
SHA256: 687abcd64141cb9d12cc1e65396aeeab45c193e1a9d3acd306d0f2fbad33b4a1
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.
Thank you,
Jason Donenfeld
-----BEGIN PGP SIGNATURE-----
iQItBAEBCAAXBQJYAQJ3EBxqYXNvbkB6eDJjNC5jb20ACgkQSfxwEqXeA66dsQ/+
NtqN/lZ83hgqnTbcA4gV3809e0PSXWem/agHL3yWpNQkX9p6PqQ1nDhjuFvpBZTJ
e7KBmsPzduPlGZmLBm8Dwc+45hS5bKEEj0w2Ed16QBfucUFlV6CeW/79945sRNEL
jBASkLrHKYAgfmCSlG6TDn43GdpLJvtzVNLw4EpY1cdN6CNbA1vuOMuIF0YLV7uY
wkZDpm2YgDASMcZw6CfwVfimEmkCvNV0PGppoec6yqq2YOtvhTSU431ye1SEa3Bt
dCT6nJIe5ZjdAFHn4KBxyrccj2TzVDbkruMfYVVekCrxftc3Fj8vQ5yc29DRG4mk
Bf6IXQLkSKR26Iju8VoFK+Uz7bAukGhXw3Dy8OdCWHmB5/Efp02xq7cXg+quosjY
KTZ+tzYmg8Oqi86MIw3WXSHOLd/IjOs+VkXb27EdKyAdgZ5J7Up3W14Y33m01vWs
iCuCE09Cc+Z/K56XruSbPrXxnvl1Xs7ZUFCIgbaWptsgAl0ftAd4NVg3r629pdMm
Dqt1LEwauGxO+bhkk3GT8RiZ/Ek0PrgD9uvRI4v6KOTWZBNr8rfGNk6AigY7c91K
uq40gzij9HY22I3PEzPYiZRsjavNaQdbE0AST63W4defQ98cAMts4a8hpJtwRU5L
6Tz9BMvHhzbRg8LkuCgcy8aC7NqeWUDPqzzeR+xjmPI=
=vgVt
-----END PGP SIGNATURE-----
reply other threads:[~2016-10-14 16:06 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=ffffffffd626322a@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