From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-tools v1.0.20191226 released
Date: Thu, 26 Dec 2019 13:35:06 +0100 [thread overview]
Message-ID: <fa05a96d8708b837@frisell.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
A new version, v1.0.20191226, 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 ==
This new wireguard-tools.git repository replaces the older WireGuard.git's
src/tools subdirectory. Package managers should begin to migrate to this newer
repository for distribution packages. There should be no functional changes
from the previous 0.0.20191219 snapshot from WireGuard.git, but there may be
build nits. Please send feedback as issues may be encountered. In the coming
days, WireGuard.git's compat kernel module will also be split out to a new
repository, and an announcement email will similarly be sent. We've tried to
retain as much of the git history for the tools as possible. It's still
slightly possible that the repository may be rebased a bit during this week
and next, if we receive reports of missing history, but hopefully what's there
now will form the basis.
The versioning scheme for these will be major.minor.date -- so basically
semver, but we encode the date as the last nibble, so that it's easier for
humans to keep track of how old things are.
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.20191226.tar.xz
SHA2-256: 74be7bb41d5b8a9ef253394f47d17784ea28cce7fabda0f66ab1e209c6acd108
A PGP signature of that file decompressed is available here:
https://git.zx2c4.com/wireguard-tools/snapshot/wireguard-tools-1.0.20191226.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 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-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl4EqJ8QHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrnS6EACAEjhi3RDGPavc2gGrrPQJtdJjXEQUjnNi
8G1J6WF8F+yzpRv398vHoXgaL5BMPehqgLNflShF5+oThKc4ThPA7iCKXorc+/ZR
XLE3ajurBbD2ekKKWzzqZZmppggxP0g7suCZTF62/ThgjFSAAwLHzKBfwaGGTIRr
gkvfZ56WWdadJHBBuMpEVCXMdns25jtbNW7TC74HAeJuv7TyDMDog9iYgfPCz70P
ePmK50vX+kg8gK17ypfAFFnjPPTyHb02+s17lH2FJQNFhLRObe7cirNcE3Ny7TZH
doEIv3OdTkNkReFOjDalbzzzqLn0rgZx2WDKOMEcM7ca2A0chh4onKDNHgEE9k8G
E3SmW86h4XAqu7J5eQ2Jpys2aIr2kzNbD1RJF0p1csWKb97zmAn6ZRuN78L6fuJG
YjSvQSZY73qbAVvIYbATtGGTu1tvM9MnGROsy/QzLD7m3HSh1N7XRGfP1KV+3oy6
dSPk2WYUExIYsWSVYLl9qCr2Z1/Ubqo0AW0SlvlaT7vLlSWw0+vjfRkKQVPfUhJ1
0y7p28qAphMNuXBS3twdJOpYYNOz2t33JThIl6J3KOBA7cwUQmBWnZNhe9pKRrvt
0Dwz6RxSEGH+wbG0kZSgrS4Rl9RgJgSFAjtwaG4rqgbmsDyu+gg7sqReg6BjgxtG
v4NZkl3Hfg==
=JrF5
-----END PGP SIGNATURE-----
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-12-26 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 12:35 Jason A. Donenfeld [this message]
2019-12-26 13:11 ` Jason A. Donenfeld
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=fa05a96d8708b837@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).