From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] WireGuard Snapshot `0.0.20191219` Available
Date: Thu, 19 Dec 2019 01:15:36 +0100 [thread overview]
Message-ID: <fa04e438d58a37ed@frisell.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new snapshot, `0.0.20191219`, 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: try both iptables(8) and nft(8) on teardown
* wg-quick: linux: use already configured addresses instead of in-memory
More fixups to the firewall support in wg-quick(8).
* compat: ipv6_dst_lookup_flow was backported to 5.3 and 5.4
The primary motivation for this snapshot: new stable releases backported an
API from 5.5.
* tools: adjust wg.8 syntax for consistency in COMMANDS section
This snapshot contains commits from: Jason A. Donenfeld and Kai Haberzettl.
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.20191219.tar.xz
SHA2-256: 5aba6f0c38e97faa0b155623ba594bb0e4bd5e29deacd8d5ed8bda8d8283b0e7
BLAKE2b-256: bc3c0d3103f799288287fd9872a3eea82e1c478c1090eb0cca6bea33d5676238
A PGP signature of that file decompressed is available here:
https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20191219.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-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl36wR4QHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4Drmk0D/0UmodDIai+NfkaCHxp4qutPpdwo0/FGH/w
q45XymjDCzO6PeVOW9TiO6asC9Vbh7atkLoig23eI85AIbHZY75NpZMMtuPSIYYq
Dw5OgotK48CmrTF10wEXhp5N8pDDXxzh84PuW44P60Iyv4tZFFfYZHhh9Nwup1eR
IhKXMR0RkwtxvSgWMG5R6NZBvE+EC/gECbnz/7c5b9P2NgFem8UJbEQ6KUWLs9SI
2kA42rkRSgP/tpJvP1Dw9udjISEemr9OyK+7pxS7A53L2W86kub71AI/RK/5L6c1
2g5XCMTIhln0icnQS5OP4TQX9j0AK4N9gwI2Z3tffAeGKHlEPDVeKgcmOKSAt0y8
w7fwh7PZH7prlqiq54/o4z9KK8zSC5JqkA/IluN+NwRCq8IeSIOrm5ee/Gmb0R1b
dEh3w4mT+/ldLzwjrOChQz0brbNGSASdHP9a6NV31sHA1tdtxeUNHk6Nhl8+CqSp
tVEK9dOMsid5+8XKssiUi6KQ55r40YIRiJxtvkFsvKqyumumZExEHYMWuIkS6P1X
nmbwmAHBA7ijmRtOJ1wcyOLgWwhtrg99R8yeD6dgnEAkqoUB1CYqAbLtVTeqNCiY
sxdt23SGZZoPRbTrKnoYcptC2NHiWoQQ2tsCM2sU746iDWxg+X52h8DH4upfGKBa
SbQxrHJqoQ==
=SOBL
-----END PGP SIGNATURE-----
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-12-19 0:15 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=fa04e438d58a37ed@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.