From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-tools v1.0.20200121 released
Date: Tue, 21 Jan 2020 15:53:32 +0100 [thread overview]
Message-ID: <fa09a54905aacb71@frisell.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new version, v1.0.20200121, 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: remove pwd from compile output
* Makefile: add standard 'all' target
* Makefile: evaluate git version lazily
Quality of life improvements for packagers.
* ipc: simplify inflatable buffer and add fuzzer
* fuzz: add generic command argument fuzzer
* fuzz: add set and setconf fuzzers
More fuzzers and a slicker string list implementation. These fuzzers now find
themselves configuring wireguard interfaces from scratch after several million
mutations, which is fun to watch.
* netlink: make sure to clear return value when trying again
Prior, if a dump was interrupted by a concurrent set operation, we'd try
again, but forget to reset an error flag, so we'd keep trying again forever.
Now we do the right thing and succeed when we succeed.
* Makefile: sort inputs to linker so that build is reproducible
Earlier versions of make(1) passed GLOB_NOSORT to glob(3), resulting in the
linker receiving its inputs in a filesystem-dependent order. This screwed up
reproducible builds.
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.20200121.tar.xz
SHA2-256: 15bfdbdbecbd3870ced9a7e68286c871bfcb2071d165f113808081f2e428faa3
A PGP signature of that file decompressed is available here:
https://git.zx2c4.com/wireguard-tools/snapshot/wireguard-tools-1.0.20200121.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-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl4nEFgQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4Drtg7D/wJ0GFv2BiQVnDJwpGozfUQr8bKitCkFK/s
i++qMfo+ldw3GOk/X6sEOrho0eGvfTxMPfFTeQvyGapYTDq5nVs8neafJ0byY+4M
rWQaUs2QCUHay23O502hLFY/4SsP7nLxaE6Bx8+BaayTIZDMMix+0wPlhSvEase+
zjBmixg75KmcRPp20+dhsdja3Q3msPC6zycHNCyxRzsWLrjXtfi6O39nagmj0eac
0HBe7ZEfdUqXGijGLlda2JJFngujiInVXT6pl7xMpA8xY/mv5IsRTpRQj8xuwPFQ
uNJr9cLEt/JY9gwucXLskqHBb2dXH60ApJAkEsmVm7YyBYPhVpDk9L11fH6EU7pQ
H+0T6TBndOHf0UWFaPjKnYlABr1jJW4Y7hwn2nFj13XCyWsU+9kEUXDFtGPCf9+2
sPboK/qn+NTDzKYJcWtnOyOfTlcWwnu7D1OYNlJ+gC9vnYELAEwW9nA/rBgrUybQ
a8Lj97Nc6bZNYgauHRU2c9ajUUXwNErnU+5PRZ/cneY/A2s6MqeF8Q0iCx8EHTZC
DxfA0WkuF09l6E2QCnz0dj0kyZldSPXyezKRcupKRemSCtyx6tKP7LghMJXhjeKA
Onkaq1tq2pXEFxExMPzyqooMlZJwPa9Ub2KWQShtV6pCwTbKqUKmotQHgvn8hELU
b9OPMq96Dg==
=4Kn5
-----END PGP SIGNATURE-----
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2020-01-21 14:53 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=fa09a54905aacb71@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.