Re: [ANNOUNCE] WireGuard Snapshot `0.0.20181007` Available

[Jordan Glover <Golden_Miller83@protonmail.ch>]

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