All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [WireGuard] [ANNOUNCE] Snapshot `experimental-0.0.20161116` Available
Date: Wed, 16 Nov 2016 16:55:06 +0100	[thread overview]
Message-ID: <ffffffffd531ab9f@frisell.zx2c4.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello,

A new experimental snapshot, `experimental-0.0.20161116`, has been tagged in
the git repository.

Please note that this snapshot is, like the rest of the project at this point
in time, experimental, and does not consitute a real release that would be
considered secure and bug-free. However, if you'd like to test this snapshot
out, there are a few relevent changes.

== Changes ==

  * socket: keep track of src address in sending packets
  * socket: ensure that saddr routing can deal with interface removal
  
  This is a rather important change. WireGuard will now reply using the same
  source address on which it received a packet. This improves compatibility with
  multi-homed hosts.
  
  * debug: cleanup skb printing
  * compat: rearrange
  * tests: use private ipv6 addresses
  * tests: trim output
  * various: nits from willy
  * packets: consolidate constants
  * device: better debug message
  
  A whole series of cleanups.
  
  * device: we need NONE for libpcap
  
  In the previous snapshot, we switched to using a VOID device type, so that
  IPv6 autoconfiguration wouldn't assign a useless IP. But this broke libpcap
  and tcpdump. So, we're back to using the NONE type, and getting a useless v6
  address. This requires upstream Linux fixes to solve.
  
  * chacha20poly1305: rely on avx and avx2
  
  This works around braindead VPS providers who disable random opcodes.

As always, the source is available at https://git.zx2c4.com/WireGuard/ and
information about the project is available at https://www.wireguard.io/ .

This snapshot is available in tarball form here:
  https://git.zx2c4.com/WireGuard/snapshot/WireGuard-experimental-0.0.20161116.tar.xz
  SHA256: 69f2d0e9c15ae6518ecdf6c7b78065be3c87e11913e2054f9b1eae2d5b75904e

If you're a snapshot package maintainer, please bump your package version. If
you're a user, the WireGuard team welcomes any and all feedback on this latest
snapshot.

Thank you,
Jason Donenfeld


-----BEGIN PGP SIGNATURE-----

iQIsBAEBCAAXBQJYLIE7EBxqYXNvbkB6eDJjNC5jb20ACgkQSfxwEqXeA65ajQ/3
YIV4saHJn1KOyVVrEL4d1tDqpJDmdnE2V4IVKoNRXmipBjkGC7FhgZJIBistGyu+
FyAKd1JEhP1/AbJVbvQeXO/mJvsz+PdNKfrO75JtHO7r+dzGc+FG/mqgRgGFz5Ss
ceFmJ1bSp2kPA7hs9DzJU5hvIRZqMOGxZuyYQn7QgU7pDSg5ephBCWM24V4pKsma
pFxHXByx7bCNZhgz57p5eJ58T8acp5H3RIroLATvI4fHgdPq/UzVTYq/Zx13DUyN
Fhdgnvp07jtZ5ciWUWGyo1EA+pTSdh4mddN8VFXHwEanJ9uxfF+xDvxTI+YgE+Yr
YH5FLpAbFs1Sz7sksEjCA3qqHZAUp3sM9cg5EZezsh7k3ApwvonT+RHK75OZmGRP
zHc8jZyNfJdzMmwbEOXQfR6J8XY6TNw/kcbx3KHy9E5xj0U8uUSko+ln36aqnUfM
ApM0i4Dh5sPWpjqbAL/WgPVRUEAGUyzjg8jnRmWOLzB9Ckg44liLlfZKFhYzrhez
GwjWoJzX0th0Qvoa+pZyk5Gj4NP3cHMITZ6Jk+K4zJ2Xkpb3poA75oZMySKx6FFH
+RLtmxduTuWbE+QANUCcNHRdURm+feiCXA/b6sKlhu8154A6th/leRXyrl+vmNwJ
2LmdZQqzQdmO3sW5fzSJej0KktQqFlxUhdiMDgm2xw==
=lWeJ
-----END PGP SIGNATURE-----

             reply	other threads:[~2016-11-16 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 15:55 Jason A. Donenfeld [this message]
2016-11-16 15:57 ` [WireGuard] [ANNOUNCE] Snapshot `experimental-0.0.20161116` Available 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=ffffffffd531ab9f@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.