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:25:29 +0100	[thread overview]
Message-ID: <f3cdde24-e1f3-a3d2-e5eb-f5e285313d66@dd-wrt.com> (raw)
In-Reply-To: <1520248764.27019.10.camel@infradead.org>

google chrome warns if you try to download tunsafe. its potentially 
unsafe. :-)

Am 05.03.2018 um 12:19 schrieb David Woodhouse:
> On Mon, 2018-03-05 at 10:19 +0100, Jason A. Donenfeld wrote:
>> 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.
> I wasn't sure whether to suggest this before, but adding Wireguard
> support to OpenConnect ought to be fairly easy. We already support
> three VPN protocols, so we have a *relatively* sane distinction between
> the protocol-specific parts, and all the OS-specific tun device
> handling and other bits that would just be gratuitous wheel-reinvention
> for you.
>
> It basically gives you support for Windows, Solaris, OSX, Android and
> various BSDs for nothing. With NetworkManager support.
>
> For a client that *isn't* purely wrapping the kernel implementation, it
> probably makes sense rather starting from scratch. If anyone's
> interested in working on it, I'd be happy to give some pointers.
>
> (I've also looked in the past at adding kernel support too, for DTLS
> acceleration; I may take a look at that again.)
>
>
> _______________________________________________
> 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

  reply	other threads:[~2018-03-05 11:16 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 [this message]
2018-03-05 11:33     ` Jason A. Donenfeld
2018-03-05 11:29   ` Sebastian Gottschall
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=f3cdde24-e1f3-a3d2-e5eb-f5e285313d66@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).