Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-linux-compat v1.0.20200908 released
Date: Tue, 08 Sep 2020 18:26:23 +0200	[thread overview]
Message-ID: <0e2845d19624a97a@mail.zx2c4.com> (raw)

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

Hello,

A new version, v1.0.20200908, of the backported WireGuard kernel module for
3.10 <= Linux <= 5.5.y has been tagged in the git repository.

== Changes ==

  * compat: drop support for SUSE 15.1
  
  Now that WireGuard is properly supported by 15.2 and people have had
  sufficient time to upgrade, we can drop support for 15.1 in this compat
  module. If downstream wants to still support 15.1, they can just apply the
  revert of this commit for however long they need.
  
  * compat: backport kfree_sensitive and switch to it
  * netlink: consistently use NLA_POLICY_EXACT_LEN()
  * netlink: consistently use NLA_POLICY_MIN_LEN()
  * compat: backport NLA policy macros
  
  Backports from upstream changes.
  
  * peerlookup: take lock before checking hash in replace operation
  
  A fix for a race condition caught by syzkaller.

This release contains commits from: Jason A. Donenfeld and Johannes Berg.

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

This version is available in compressed tarball form here:
  https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-1.0.20200908.tar.xz
  SHA2-256: ad33b2d2267a37e0f65c97e65e7d4d926d5aef7d530c251b63fbf919048eead9

A PGP signature of that file decompressed is available here:
  https://git.zx2c4.com/wireguard-linux-compat/snapshot/wireguard-linux-compat-1.0.20200908.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-----

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl9XsFUQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DruUeEADc1LXeIOzKtEZnOk0gGgPfNlAH229Rzf5m
FkvRgpvCtVysf6JHo2TtsvzVYwibV1tR5HaV2J8y6u1rZZ3gWYmQKR3Eb/v7EIHD
55x689YPbv80t4bzUR691msDVfDzM8z81Y9dzWIh+qCs2FljxmGIoP2y7amXzfyP
CW4Lb1PFyfuNP+Cae7qHYrzUhwD81xzKOyJ5uaASK34iZGolqPaqKX4L+CDnDQ1x
7GZdlMo1w/raNY6I/fAffTdcyfdslXR3uNrwhrfiU1M3heKFEAxI76D+r/g0jqq2
GRCNvyr+G893sa+Xi4PD6XtbySfiYZXD9DDkG0Wo08oUy9IkxjatVRR0XZGdR9LN
U2/VmVDyWugIesrtr3C0hW69TZ2e85TVbLCkK0KdUYpl+VUjX2FlUwXJT5PqbIDf
161Jw6alvK89hNMC2tfgOAN794trQRdA/UPoBNazOW2P9WI5Al98K1g+haLyCUot
SP2xYFr3TqNmF9oNSBpj/RyKoExsYjSQTk34tmWTE1gQRBNXxkFzbCPGEf4BCF6j
BQXEomRrUA4AHkwKzk4hsrFAyxxBwOBc9+L8fC0M319iZsVCNd0bBGXuVMQ3K+Vp
SxSHUjd24Ns78LQJzR8rawMehZIe5tSeXnDAuTUkr+qwOYAE0MmjKkrFBUbsrDMu
9ECSppmVWw==
=f923
-----END PGP SIGNATURE-----

                 reply	other threads:[~2020-09-08 16:26 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=0e2845d19624a97a@mail.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).