From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-tools v1.0.20210424 released
Date: Sat, 24 Apr 2021 16:44:22 -0400 [thread overview]
Message-ID: <8ee718aff5086347@lists.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new version, v1.0.20210424, 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 ==
* wg-quick: freebsd: check for socket using -S, not -f
* wg-quick: freebsd: do not assume point-to-point interface flag
* wg-quick: freebsd: use ifconfig for determining if interface is up
* wg-quick: kill route monitor when loop terminates
These three fixes affect FreeBSD, OpenBSD, and Darwin, and are little cleanups
around wg-quick.
This release contains commits from: Jason A. Donenfeld.
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.20210424.tar.xz
SHA2-256:
A PGP signature of that file decompressed is available here:
https://git.zx2c4.com/wireguard-tools/snapshot/wireguard-tools-1.0.20210424.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-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAmCEgyEQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrtGEEADJzVkTM19/miDZ3G89FpxtZU5/g+d9F47o
8gJSns642FJS0cC6HllqlYLL7bxgvBkXRVPkmnDGoDrqgrJWB+bnOKFOdtfKXv1f
Ar7QREL+2ZLfCw9NgkFWwBS3NxxCFbyHm8AjK1vAAcjISRpH3GJDzjspuzmfKqzs
bvyQ8U05Tkbvc0J6lLd3A4ei1q+JxJXTgoneWviVNEuDn5Jj8/oEqoRAJbN8d8pq
pB5C7DgbfNnPiX/2bnw+frskUgwU043n7fYHr41mCUTdKTst26DrPEOgR0ebiKU2
XGlBgHziJJoeciealqXRhPb+DFKj1FvfEozvcuYQbAPUvs1qX44gWDVcUBEXX5TJ
GAh1vVSebLuwM17J4J5zVw66pKjTnZaNIJRPA8qdaHB1/uB/ZZNnYl6DPd+OaJTN
170/HaId2iGtROGljOnojGeu/CMx+VEwv+L1WDfr9ubgd1p+N7m3YpJgsP6JutyX
b9Ff3mbERy3aKmH37CYFeQS3TG8e5pHfMJR2QwV2M1PWK0BleWE1vHk9MdImy4u8
rghju4MBEb16xdJbJcqillKG/F0j/AQdlbVbwItO57iwfT07V6NNuElpaUizwcps
obfYjqLFQ0wt0nEWTB5OxON2+E4c0YgbcZrDJFMmoYxXwlD27K8IjJM4E0zzg0vA
a6IU8oxLqg==
=36NL
-----END PGP SIGNATURE-----
reply other threads:[~2021-04-24 20:45 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=8ee718aff5086347@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.