wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: s.gottschall@newmedia-net.de
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard not coming up on DD-wrt
Date: Tue, 9 Oct 2018 21:18:54 +0200	[thread overview]
Message-ID: <CAHmME9oKzPdrGRibiA7_gB=qZP4qcKkN35-ZAoFkSEeV-wDXyw@mail.gmail.com> (raw)
In-Reply-To: <796625c4-d114-1b5f-ea79-97b91e682549@newmedia-net.de>

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

  reply	other threads:[~2018-10-09 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 15:06 Wireguard not coming up on DD-wrt Dennis van J.
2018-10-09 16:29 ` Sebastian Gottschall
2018-10-09 19:18   ` Jason A. Donenfeld [this message]
2018-10-10  6:00   ` Dennis van J.
     [not found]     ` <08ebe77e-c66f-a356-8a42-e0a0d920a2a8@newmedia-net.de>
2018-10-10 13:31       ` Dennis van J.
     [not found]         ` <b6289282-309d-9e23-a31f-4960872ab522@newmedia-net.de>
2018-10-10 14:52           ` Dennis van J.
2018-10-10 15:51   ` route_allowed_ips on on openwrt Emanuele Bernardi

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='CAHmME9oKzPdrGRibiA7_gB=qZP4qcKkN35-ZAoFkSEeV-wDXyw@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=s.gottschall@newmedia-net.de \
    --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).