[ANNOUNCE] WireGuard Snapshot `0.0.20181007` Available

[ANNOUNCE] WireGuard Snapshot `0.0.20181007` Available

[Jason A. Donenfeld]

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

Hello,

A new snapshot, `0.0.20181007`, 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. WireGuard is generally thought to be fairly
stable, and most likely will not crash your computer (though it may).
However, as this is a pre-release snapshot, it comes with no guarantees, and
its security is not yet to be depended on; it is not applicable for CVEs.

With all that said, if you'd like to test this snapshot out, there are a
few relevant changes.

== Changes ==

  * makefile: do more generic wildcard so as to avoid rename issues
  
  Yesterday's snapshot broke DKMS installation, which is the majority of distros
  using WireGuard, so we're rushing out a fix the day after so that people can
  actually run it.
  
  * compat: account for ancient ARM assembler
  * compat: make asm/simd.h conditional on its existence
  * compat: clang cannot handle __builtin_constant_p
  
  Yesterday's snapshot broke old ARM kernels and Android kernels using Clang.
  
  * crypto: disable broken implementations in selftests
  
  If the selftests determine a particular crypto implementation doesn't work, it
  prints a warning -- since that would be a pretty grave bug -- but it also just
  disables that implementation so that we don't compute anything incorrectly.
  
  * crypto: use BIT(i) & bitmap instead of (bitmap >> i) & 1
  * allowedips: document additional nobs
  * crypto: clean up remaining .h->.c
  * global: style nits
  
  Various cleanups and style nits.

This snapshot contains commits from: Jason A. Donenfeld.

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

This snapshot is available in compressed tarball form here:
  https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20181007.tar.xz
  SHA2-256: d26e0d1216594871b5947e76d64c2fa50e9b34b68cdcfa3fdad588cbb314af89
  BLAKE2b-256: 50dc7e09513cac1bd9de1bf136bae4d595bb0d27afebc33dab6c3bbbb3bca175

A PGP signature of that file decompressed is available here:
  https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20181007.tar.asc
  Signing key: AB9942E6D4A4CFC3412620A749FC7012A5DE03AE

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.

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-----

iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAlu6JCsQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrtPqEADNTNN6sqqEy66hp5mtK9BhCMMcPNlErVv2
9wXFoX9bhQ2fdYWdKBuP9tOhvWtYmGpME8nWR3x5Y7wEjOFnvLWXxOoatxSuxFAA
KF1WDXWuswbXq5bxY4J1xO4kYO2BxrJLn2eaIH1Zh+uAEFEbxsHBy2rmvuM+s7Rq
YvL628nVuWce1lETBqq2rx2dBR1vgF5O1eAsDreXrDrl4LpcPdQlhiKcrS57b68x
Jkpsz5Yjm4T+czInqO6pQs+Yr0v9WckgMoMqGEombkyLiG6d4e1SZBzrnqG7JY4X
ZV85WxU77Qsy3xpWkNHwl6pmCAw2DwcPRB+rmxyWMhw0bI3IGPYhRAKo8nt/mOod
zS0KIqE0IcNOip6/IKobiYBlt0ZF5QxUkgk9NgeTnPndyoXSo5OV5qD5hiTXxJ+O
Vxfac8TbBn/xLEhkckhP9Y3k8Sl44JfCwfWp9NS+d7oLWORLVUbzWItvADYkFto1
VjwBYQPqYhyk5bfY70iDiQSnIJfmhCGzcAtCI/0RBIK/Nj39QL0cu2xKAGwiR6Lc
FhzoBT3x9KdvzlZTt4nqh3aAH4U1LwGgv3/Z+WHNhBFeKp4ctA+YlYvCeWHwH5Hj
hnKW9ZiKyjfdRumEuADomD9U1J8GTrbXf02mreKQ+Z+0ucfdqI3cvH3orErbHIXD
Q91QHvUoSw==
=5jxP
-----END PGP SIGNATURE-----
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: [ANNOUNCE] WireGuard Snapshot `0.0.20181007` Available

[Jordan Glover]

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, October 7, 2018 5:20 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> Hello,
>
> A new snapshot, `0.0.20181007`, 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. WireGuard is generally thought to be fairly
> stable, and most likely will not crash your computer (though it may).
> However, as this is a pre-release snapshot, it comes with no guarantees, and
> its security is not yet to be depended on; it is not applicable for CVEs.
>
> With all that said, if you'd like to test this snapshot out, there are a
> few relevant changes.
>
> == Changes ==
>
> -   makefile: do more generic wildcard so as to avoid rename issues
>
>     Yesterday's snapshot broke DKMS installation, which is the majority of distros
>     using WireGuard, so we're rushing out a fix the day after so that people can
>     actually run it.
>
> -   compat: account for ancient ARM assembler
>
> -   compat: make asm/simd.h conditional on its existence
>
> -   compat: clang cannot handle __builtin_constant_p
>
>     Yesterday's snapshot broke old ARM kernels and Android kernels using Clang.
>
> -   crypto: disable broken implementations in selftests
>
>     If the selftests determine a particular crypto implementation doesn't work, it
>     prints a warning -- since that would be a pretty grave bug -- but it also just
>     disables that implementation so that we don't compute anything incorrectly.
>
> -   crypto: use BIT(i) & bitmap instead of (bitmap >> i) & 1
>
> -   allowedips: document additional nobs
>
> -   crypto: clean up remaining .h->.c
>
> -   global: style nits
>
>     Various cleanups and style nits.
>
>     This snapshot contains commits from: Jason A. Donenfeld.
>
>     As always, the source is available at https://git.zx2c4.com/WireGuard/ and
>     information about the project is available at https://www.wireguard.com/ .
>
>     This snapshot is available in compressed tarball form here:
>     https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20181007.tar.xz
>     SHA2-256: d26e0d1216594871b5947e76d64c2fa50e9b34b68cdcfa3fdad588cbb314af89
>     BLAKE2b-256: 50dc7e09513cac1bd9de1bf136bae4d595bb0d27afebc33dab6c3bbbb3bca175
>
>     A PGP signature of that file decompressed is available here:
>     https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20181007.tar.asc
>     Signing key: AB9942E6D4A4CFC3412620A749FC7012A5DE03AE
>
>     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.
>
>     Finally, WireGuard development thrives on donations. By popular demand, we
>     have a webpage for this: https://www.wireguard.com/donations/
>
>     Thank you,
>     Jason Donenfeld
>

I got an error when doing in-tree build using WireGuard/contrib/kernel-tree/create-patch.sh

net/wireguard/receive.c:338:10: fatal error: selftest/counter.c: No such file or directory
 #include "selftest/counter.c"
          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.

Jordan
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: [ANNOUNCE] WireGuard Snapshot `0.0.20181007` Available

[Jason A. Donenfeld]

On Sun, Oct 7, 2018 at 10:49 PM Jordan Glover
<Golden_Miller83@protonmail.ch> wrote:
> I got an error when doing in-tree build using WireGuard/contrib/kernel-tree/create-patch.sh
>
> net/wireguard/receive.c:338:10: fatal error: selftest/counter.c: No such file or directory
>  #include "selftest/counter.c"
>           ^~~~~~~~~~~~~~~~~~~~
> compilation terminated.

Youch. I'm rewriting those scripts so that it picks up file name
changes like this automatically, so it's not such a whack-a-mole
situation.

Let me know if this fixes it:
https://git.zx2c4.com/WireGuard/commit/?id=28366408148d0f230daebd9a61c5f7bf0c3e0390

Jason
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: [ANNOUNCE] WireGuard Snapshot `0.0.20181007` Available

[logcabin]

I get this when building on armv7, but it doesn't seem to affect the build:

echo '  Building modules, stage 2.';
make -f ./scripts/Makefile.modpost
grep: ./arch/arm/Kbuild: No such file or directory


On Sun, Oct 7, 2018, at 6:37 PM, Jason A. Donenfeld wrote:
> On Sun, Oct 7, 2018 at 10:49 PM Jordan Glover
> <Golden_Miller83@protonmail.ch> wrote:
> > I got an error when doing in-tree build using WireGuard/contrib/kernel-tree/create-patch.sh
> >
> > net/wireguard/receive.c:338:10: fatal error: selftest/counter.c: No such file or directory
> >  #include "selftest/counter.c"
> >           ^~~~~~~~~~~~~~~~~~~~
> > compilation terminated.
> 
> Youch. I'm rewriting those scripts so that it picks up file name
> changes like this automatically, so it's not such a whack-a-mole
> situation.
> 
> Let me know if this fixes it:
> https://git.zx2c4.com/WireGuard/commit/?id=28366408148d0f230daebd9a61c5f7bf0c3e0390
> 
> Jason
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: [ANNOUNCE] WireGuard Snapshot `0.0.20181007` Available

[Jason A. Donenfeld]

On Mon, Oct 8, 2018 at 12:44 AM <logcabin@fastmail.net> wrote:
>
> I get this when building on armv7, but it doesn't seem to affect the build:
>
> echo '  Building modules, stage 2.';
> make -f ./scripts/Makefile.modpost
> grep: ./arch/arm/Kbuild: No such file or directory

Fixed a few hours ago in the master branch. It won't affect the build, however.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: [ANNOUNCE] WireGuard Snapshot `0.0.20181007` Available

[Sebastian Gottschall]

i do not use the defined master. i just checkout the git revisions 
defined by your snapshots. but since you release snapshots  2 times per 
week sometimes its still ends up on a heavy changing module
but that should not be the topic here. the topic is what leads wireguard 
to fail on his system. so we need to track down first which hardware he 
is using since i do support alot of devices with alot of different cpu 
platforms. so please stay on topic and do not speculate too much


Am 09.10.2018 um 21:18 schrieb Jason A. Donenfeld:
> On Tue, Oct 9, 2018 at 6:30 PM Sebastian Gottschall
> <s.gottschall@newmedia-net.de> wrote:
>> just to make sure. since i'm updating wireguard in dd-wrt very often to the latest state of art code from git.
> Do not do this. Rather, use snapshots. If you're distributing builds
> based on git master, you're putting your users at unnecessary risk.
> The only safe and acceptable distribution of WireGuard is using the
> latest snapshot tarball. When you use git master, you're not getting
> the "latest state of art code", you're getting "jason's 5am
> force-pushes and wacky ideas pre-codereview." On the other hand, when
> you use snapshots, you're getting code that I've spent some time
> reviewing and double checking to make sure it won't murder kittens and
> related atrocities.
>
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: [ANNOUNCE] WireGuard Snapshot `0.0.20181007` Available

[Jordan Glover]

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, October 8, 2018 12:37 AM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> On Sun, Oct 7, 2018 at 10:49 PM Jordan Glover
> Golden_Miller83@protonmail.ch wrote:
>
> > I got an error when doing in-tree build using WireGuard/contrib/kernel-tree/create-patch.sh
> > net/wireguard/receive.c:338:10: fatal error: selftest/counter.c: No such file or directory
> > #include "selftest/counter.c"
> > ^~~~~~~~~~~~~~~~~~~~
> > compilation terminated.
>
> Youch. I'm rewriting those scripts so that it picks up file name
> changes like this automatically, so it's not such a whack-a-mole
> situation.
>
> Let me know if this fixes it:
> https://git.zx2c4.com/WireGuard/commit/?id=28366408148d0f230daebd9a61c5f7bf0c3e0390
>
> Jason

Yes, this fixes this issue. Thank you.

Jordan
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard