Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Tunsafe Windows client for wireguard (not opensource yet they say
Date: Mon, 5 Mar 2018 12:29:10 +0100	[thread overview]
Message-ID: <8f4c1033-d41c-e358-58f2-cd02618e5e82@dd-wrt.com> (raw)
In-Reply-To: <CAHmME9r95cjSXK8YitGuHxFp0EfrMKhQEGXL5Ux=rMXLt=U5FA@mail.gmail.com>

it isnt closed source. the sourcecode is provided as far as i have seen 
and licensed under GPL
but correct me if i'm wrong
https://tunsafe.com/downloads/TunSafe-TAP-9.21.2-sources.zip

Am 05.03.2018 um 10:19 schrieb Jason A. Donenfeld:
> Hi Henrique,
>
> Thanks for posting this.
>
> Please stay away from this software, and generally be wary of
> closed-source WireGuard implementations trying to fill the void. This
> one was written by a community-unfriendly proprietary author, and
> we've got little way of ensuring protocol compliance or basic
> security. Especially from my discussions from him, it's clear what
> he's up to, and this seems like some nastiness. Should I spend my time
> reverse engineering this software and discovering zero-days? Probably
> not a good use of my time, despite my usual love of this sort of
> thing.
>
> One aspect of the WireGuard project is that we're taking development
> very carefully and slowly, not jumping to premature releases, and
> really studying every bit of what we produce in order to ship the
> least-vulnerable and most-correct code we possibly can. We're still
> shipping code -- it's not an approach that results in a complete
> standstill -- but it does mean that in these intervening periods,
> there will be propheteers and cowboys coming out of the woodwork to
> fill the void.
>
> It's quite easy to make a tiny tunneling protocol that's reasonably
> fast and does a few things; if you look on Github there are hundreds.
> It's quite another thing to write robust and secure software intend to
> last for a long time. That's what we're working on here.
>
> Fortunately we have two very nice projects that are rapidly
> approaching maturity: one in Go and one in Rust. I fully welcome
> future OSS authors into the project. When I'm back from visiting
> family at the beginning of April, I think we'll be in a good place to
> have a few first releases.
>
> I'll also do what I can to see that people aren't peddling junk and
> calling it wireguard, so as to reduce user confusion, but this of
> course isn't a very easy endeavor. I'm open to suggestions on how to
> approach this.
>
> Regards,
> Jason
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>

-- 
Mit freundlichen Grüssen / Regards

Sebastian Gottschall / CTO

NewMedia-NET GmbH - DD-WRT
Firmensitz:  Stubenwaldallee 21a, 64625 Bensheim
Registergericht: Amtsgericht Darmstadt, HRB 25473
Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.dd-wrt.com
email: s.gottschall@dd-wrt.com
Tel.: +496251-582650 / Fax: +496251-5826565

  parent reply	other threads:[~2018-03-05 11:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05  8:26 Henrique Carrega
2018-03-05  9:19 ` Jason A. Donenfeld
2018-03-05 11:11   ` Henrique Carrega
2018-03-05 11:19   ` David Woodhouse
2018-03-05 11:25     ` Sebastian Gottschall
2018-03-05 11:33     ` Jason A. Donenfeld
2018-03-05 11:29   ` Sebastian Gottschall [this message]
2018-03-05 11:31     ` Jason A. Donenfeld
2018-03-05 11:29   ` Sebastian Gottschall
2018-03-06  1:44 Ludvig Strigeus
2018-03-06  9:16 ` Jason A. Donenfeld
2018-03-06 12:32 ` Steffan Karger

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=8f4c1033-d41c-e358-58f2-cd02618e5e82@dd-wrt.com \
    --to=s.gottschall@dd-wrt.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).