From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [WireGuard] [ANNOUNCE] Snapshot `experimental-0.0.20160708.1` Available
Date: Fri, 08 Jul 2016 16:37:23 +0200 [thread overview]
Message-ID: <278721635a23c243@frisell.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new experimental snapshot, `experimental-0.0.20160708.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 ==
* persistent keepalive: start sending immediately -- the previously released
feature was not useful without this extra commit. So, getting this in here
now so that people can actually test this out. Sorry for the churn. Don't
bother packaging the previous snapshot.
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.20160708.1.tar.xz
SHA256: 11faf795dd45ff0d13cdd204775b07e01fda596b4a9c2a1b326614c226e9725d
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-----
Version: GnuPG v2
iQItBAEBCAAXBQJXf7p+EBxqYXNvbkB6eDJjNC5jb20ACgkQSfxwEqXeA66C1BAA
r3VYAPR7CNx5j93fK+tTdbotRT/OwVMntgI6Rwy/JgDX6lyGofcwZsGPv8EsKH2j
FSozoC4eCabG1Oq+Rjvh9Hpr+H50tJMruiICodRgKLVQkpQNPzl3XDI1u0nZRxkh
H8N7i9/PWIyCGbQXlSQJjWaYu8/n+qE7rfTDnCfedi2vPyKXR9STKEO14It9brM6
FK/5s9+LQH7wWVSawTPQJIo8G7lZUxJHYMe6Ipb26tXFvyup+D7vvlzVaP0Nfb7x
R67Fly9iBTPjS0eqUaZes+JHZUMQ/T7St5HZ4Xg+diDmjDzuhlHG1i5YyY94NEfA
/D/3MyTMaO6j3kGSIQmKM7kiI2+ngkOaj5tKSqNua+USpiL8v4461m5Jti1psNwA
mm/Qw+MROUz4zkXsMHtN97DSCK+66MVRFB023FI8Ol0Wwitp9RAm57jQWRu+Meij
Vor57Q5SD+299xb0CciNjh1neBlRirkA6fG3RZM4WyUnD7qoR8o3c+ezXslj6qur
giXMZTTb2+BdCgV+w0Z7blHFKqR0PvW8ehJoFPsU5GSAcZ20ucGmZ33Z/gFE5WLQ
QPO4Rzj6Nq4SxWDHwBuo0UaRr28i0tGM7nUJaSjalB7NZ9ZcAf/jMLwkGpJTeCzn
zirmZfYGs2+EviiOE4jX+2cp/AXn5x5xg5EGymxCOD0=
=zcDL
-----END PGP SIGNATURE-----
next reply other threads:[~2016-07-08 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 14:37 Jason A. Donenfeld [this message]
2016-07-08 16:23 ` [WireGuard] [ANNOUNCE] Snapshot `experimental-0.0.20160708.1` Available Bruno Wolff III
2016-07-08 17:55 ` Jason A. Donenfeld
2016-07-08 18:49 ` Jason A. Donenfeld
2016-07-08 19:55 ` Bruno Wolff III
2016-07-08 20:21 ` Jason A. Donenfeld
2016-07-08 20:44 ` Bruno Wolff III
2016-07-08 20:54 ` Bruno Wolff III
2016-07-08 21:45 ` 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=278721635a23c243@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