From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [WireGuard] [ANNOUNCE] Snapshot `experimental-0.0.20161116.1` Available
Date: Wed, 16 Nov 2016 21:48:35 +0100 [thread overview]
Message-ID: <cec8808b1779fac9@frisell.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new experimental snapshot, `experimental-0.0.20161116.1`, 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 ==
The earlier snapshot today broke some builds on kernels <= 4.3. Packagers only
need to bump versions for this single commit if distribution kernels use <=
4.3. Sorry for the inconvenience.
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.20161116.1.tar.xz
SHA256: 730d9d919e1942cf83e59dcb8c6ee6ac6696c62ce363c4802474774a5db8238d
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-----
iQItBAEBCAAXBQJYLMYdEBxqYXNvbkB6eDJjNC5jb20ACgkQSfxwEqXeA67lEQ//
cnsPZPkxaKPCPOB1e26QJgH9SrCVvNanQA7EZTqWd7nH9n6u86TtrFFoGu3uqLR6
PqHczaEkYzH0rWXwX+tQgtMS6IbprA54hEzMMAFBiTfymkYpbU5A5oDAUTOfuZNm
T4wnCE1VVtzc7aac2gx4FOOewJL2imV7+TvtSvvOgycWA3EKD1KmKfp89nv9QzRo
NDhGMjBzTjZ2LZt/V3+TCbo8War2eNNaz9TuFN10iMCrrJd1c1B8Sst67fjqS6F5
uDv0cCTYqrE11q7HWlFri77A3KcG/rp/DwDBBFEpjIXpoTlD7OWCctxdsT0W9bsZ
3uACS+wBmnqoDWe4zDtx5jSUq+reRgbcdGeA0hkhq2Z+nD7CAqkS1FyRpqOQGrxc
4XUt2agTPxCe/E3PctZ3eDSNf2scL+kX+d1VbDhcq/++Wr/KhaUwj+FysdYL70Bk
pb0Yl/E8Xqp9aMmdR9OteQxGU/VUcNq/1rO1HmyFbJbafKEyDNN/JPVs8PX1EzW7
YGPHz8gb6GB6OFLyIOUNq8NhtXNZb4s529jAoPFdnHFroQHZAiv0hi9E5iMICECl
qmc4pWI8KRcbLujiordT1Eld1RDr+J9MHXvGpJt9xpmaok5PaD8u3sivbhzWRlVB
5zSRWJ0CzXPRdJS1r3Ep/TRhL5dij6AvpCM6+myDFag=
=bJmA
-----END PGP SIGNATURE-----
reply other threads:[~2016-11-16 20:45 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=cec8808b1779fac9@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).