From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-tools v1.0.20200319 released
Date: Thu, 19 Mar 2020 16:48:57 -0600 [thread overview]
Message-ID: <3883012e23755f3c@frisell.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new version, v1.0.20200319, of wireguard-tools has been tagged in the git
repository, containing various required userspace utilities, such as the
wg(8) and wg-quick(8) commands and documentation.
== Changes ==
* netlink: initialize mostly unused field
* curve25519: squelch warnings on clang
Code quality improvements.
* man: fix grammar in wg(8) and wg-quick(8)
* man: backlink wg-quick(8) in wg(8)
* man: add a warning to the SaveConfig description
Man page improvements. We hope to rewrite our man pages in mdocml at some
point soon.
* wincompat: use string_list instead of inflatable_buffer
* wincompat: use new protected prefix on Windows
These get wg(8) running again properly on Windows.
This release contains commits from: Jason A. Donenfeld, Luis Ressel, and Kai
Haberzettl.
As always, the source is available at https://git.zx2c4.com/wireguard-tools/ and
information about the project is available at https://www.wireguard.com/ .
This release is available in compressed tarball form here:
https://git.zx2c4.com/wireguard-tools/snapshot/wireguard-tools-1.0.20200319.tar.xz
SHA2-256: 757ed31d4d48d5fd7853bfd9bfa6a3a1b53c24a94fe617439948784a2c0ed987
A PGP signature of that file decompressed is available here:
https://git.zx2c4.com/wireguard-tools/snapshot/wireguard-tools-1.0.20200319.tar.asc
Signing key: AB9942E6D4A4CFC3412620A749FC7012A5DE03AE
Remember to unxz the tarball before verifying the signature.
If you're a package maintainer, please bump your package version. If you're a
user, the WireGuard team welcomes any and all feedback on this latest version.
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-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl5z9tEQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4Drk83D/9j7/mBwVTqbEcfMwpsR9S26pveNVuN/kml
wH5WZ4G2Z/RJQQ5GiV6cc0ne2e1SrT0UfJsPc35GS42TihHvcKC41gZICapCNOIl
uC9Xo8y3iseNwvxkcMw5TdWcpEZIOaEUOGY5+bDlwsPp9s0dN9+nY76cAY/5uOrZ
05x0ILCyC3yDOaW3dtxhBq3ahP6jowS2dNLECRNIyvsHxUeFosxSdkQPh5PmlK6L
/+GdlA3dWwm8fzpMiZsOGVrjoDtRZB4M9FOB10uj1Uvmxz9v2EXWx54cRbKCjBff
u2PgUguOTuCvVwSWukzD2pk4a0iKv+O1sTFc1s2/oURPeWBBjZoApd7xHNzpTiHB
UGckmxU/pSbEdH3tZFf3AG5tg9iMPNC+XYJZpBWrorGxkYbgzcBg9x1T3l/GYprC
OyayVe3qPNZVLLPAnK8cAvsJ82jPhwJnAFLO5DTKWMtFcueyTHmyl22Qsz46aiOA
VDXE9YYNx2HIK/2ELuXRoHbnEftmqXif4zwOzikhbxR2pygIQIa2pkSzbmeaXJOR
3Fw9HhdJ70tq2/ZKlHVo5FnzO/ZmgznYNAgOGYJM2J62x054NxMVF0YCGt4YkUgR
OWyF1jsYoKtWsHyWlVFVUxo4rAuNYmbFnvhtwoGVLhyT0ganjXzr8b5590GJXlU9
hDxgs4tnyQ==
=BBmE
-----END PGP SIGNATURE-----
reply other threads:[~2020-03-19 22:49 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=3883012e23755f3c@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).