[ANNOUNCE] WireGuard Snapshot `0.0.20181007` Available
s.gottschall at newmedia-net.de
Wed Oct 10 00:29:21 CEST 2018
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 at 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.
More information about the WireGuard