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

On Mon, Mar 5, 2018 at 12:29 PM, Sebastian Gottschall
<s.gottschall@dd-wrt.com> wrote:
> 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

This isn't the source code of tunsafe. This is the source code of the
OpenVPN Windows tuntap kernel driver, which has been hacked up in
various ways for tunsafe. That's a super scary driver, by the way.

The actual source code of tunsafe is closed source.

  reply	other threads:[~2018-03-05 11:22 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
2018-03-05 11:31     ` Jason A. Donenfeld [this message]
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='CAHmME9pMfRvEMeGVysnKV+s7sFOv0t=za0kVHGhwZgEWoYKEqw@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=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).