From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] WireGuard Snapshot `0.0.20170214` Available
Date: Tue, 14 Feb 2017 11:58:09 +0100 [thread overview]
Message-ID: <0a706c552ce5da44@frisell.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new snapshot, `0.0.20170214`, 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. WireGuard is generally thought to be fairly
stable, and most likely will not crash your computer (though it may).
However, as this is a pre-release snapshot, it comes with no guarantees, and
its security is not yet to be depended on; it is not applicable for CVEs.
With all that said, if you'd like to test this snapshot out, there are a
few relevent changes.
== Changes ==
* wg-quick: unquote fwmark for bash 4.3
Whoops. This is a super quick snapshot to unbreak things on
machines running old bash. Sorry about this.
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-0.0.20170214.tar.xz
SHA2-256: 1e4ee213d2a5ac672c952c59e9c64d6d7d5dc3e21c003aee30d75208237e8bf5
BLAKE2b-256: 1d3c934d020a2daa984d1002f7dbcebaa3c0f57d295e9b975b1322a0e6d74a4a
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-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAlii4rwQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrtLoEACeA9oTyVMFMxDWnAtbqwln/qR0iPWu6XeJ
pcAwusz+1OrZGt446PJbMaohILa7IH0Fm33foJr2vRjKD4rJTvClk4cnUZDnl1hX
Pr0qKP+4vQVPwB4RlNxHKgJIgvTVJQysk/f90hHZQZth1+cNBV+VSbP/4rmoW8YZ
FKLFRqe5C+U7BAS1StGZLJA+PFmkKWRDHEDMc89CdvdqKFJ3F2UVNvbZ/s3iwies
+IQseT7Sqqow04blnvADqOcUvf3cWRyqA9LPkX9HLUG5C+1GeZ+/Cjlo+2H1bdrT
MQibWWv6UbZNfINeWUgrXwU6MKW1Yo4ZpuCsLG932zdESGkDHHpYQbl65Y0Av/On
n52nkaKxh5pkK9/10UtzCMYlhTV2sLlZ9Pz6+r5ZCcwGdNolykrg7+7iq6ZVTo7B
Xoeiu0RAuh9vlXWXIEEHzqlASXeRDr68qqYKnAu7JvE03qcFXx1ycVdCXfs8/ON8
7q5LsHte4AmKCj/pB2rPg3vJVkAVRKNsz4QJ316ToOBsfao6FLrE3M40u8TTDI8W
P76oObeOQ7bkivjjJDpWyvLmnVHwqR1CMLBY7d7N7yN1DATLvEShp23O82bvOcec
tfmeutPBBdHjwptNqAYD22jwem1RQjmWd4lE8trMHGtSWcpIAyqULxrWRldn33AC
7uxubU9HVw==
=3aw0
-----END PGP SIGNATURE-----
reply other threads:[~2017-02-14 10:44 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=0a706c552ce5da44@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.