From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-tools v1.0.20210315 released
Date: Mon, 15 Mar 2021 08:16:55 -0600 [thread overview]
Message-ID: <200fe853c7f21359@lists.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new version, v1.0.20210315, 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 ==
* Makefile: fix version indicator
This lets releases be untar'd into existing git repos without accidentally
picking up that repo's version number.
* wireguard-tools: const correctness
* wireguard-tools: drag in headers for prototypes
Cleanups, thanks to verbose warnings on FreeBSD's clang.
* ipc: uniformly ignore preshared keys that are zero
Shouldn't have a practical effect, but fixes correctness on OpenBSD.
* wg-quick: freebsd: add kernel support
* ipc: freebsd: add initial FreeBSD support
* wg-quick: freebsd: avoid writing private keys to /tmp
We now support FreeBSD! I'll send an announcement soon with details, but Kyle,
MattD, and I worked tirelessly to get FreeBSD's kernel implementation up to
snuff and well supported:
https://cgit.freebsd.org/src/commit/?id=74ae3f3e33b810248da19004c58b3581cd367843
This release contains commits from: Jason A. Donenfeld, Kyle Evans, and
Florian Eckert.
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.20210315.tar.xz
SHA2-256: af001d5492be6bf58ef0bebe04b446b6f50eb53e1226fab679cc34af40733a22
A PGP signature of that file decompressed is available here:
https://git.zx2c4.com/wireguard-tools/snapshot/wireguard-tools-1.0.20210315.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-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAmBPbE0QHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DruifEADUwp1ZjLW4HBrdefitdFS15AsRtZCYcXWn
PyxaTf/tTjeZMbVgkLh0vSOp+xOxRU6MfdtIvUK7I8dCotmI6ddtS11UjyuSmLjZ
CQA4nmKQoQJ2HeohksCWZDzEFWYKeRsCmzOk39qYFVz2xeAS3YLpuTgRP6jpdgal
o1gDty4A1vNt3nAuRPYMJHx1kBC5+nhvACv25270tf5CLuBvi6+VVHkPsSEl9rOY
XSQtXZrhza/0l82dN8gxkx7D4XmF60NhN8kbaX7V/lVX3ogagP2jSIjkk1xSMbX/
qpPRLod/5IMweA3t2YtQvHnkhBCjSt4jGvFqQJv6bPDKHtNgxYvRYX+gbVF0qBlB
6PZLq1s9fazOD8kCWbY4MV0E+/JbYc6ee8ILI7f2wCVQhKcQiRSiVhYetbenVJzC
7vg1s9sU0i4YpZ/obtNIXuNhfqX0RCa5Q7r3CLpkOOGY7/I05evqakcNNjwtSb8E
W2E8eJ8+bz9Gr5ltqZ56+HA3qvo/tIuqfAYMdITrvEv/TkWMHcaP03qbYNoz4ECG
3zCtJXqXMHNR/mw5vqnKxL8RLoLsdeaR5iU1G2gy9HECzs8iElQijMAgzSJT2MYU
vO8la63vpWa5Fs9YFDQ9CrBPeHNpeDw2mkNYNalLreeMEZW19rGaQK2xser6Jle8
S/BJJp7nfw==
=08Wx
-----END PGP SIGNATURE-----
reply other threads:[~2021-03-15 14:19 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=200fe853c7f21359@lists.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.