Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Maximilian Moser <e1326252@student.tuwien.ac.at>
Cc: Jordan DeBeer <debee1jp@gmail.com>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: NetworkManager Plugin
Date: Thu, 15 Feb 2018 15:07:54 +0100	[thread overview]
Message-ID: <CAHmME9rZU8y8mjHhHkVJ9foRW8Wuk5QMoijMfVU=_4LHfg7F-w@mail.gmail.com> (raw)
In-Reply-To: <cba131ba-cd15-8bf4-cdd1-4d46ad774d41@student.tuwien.ac.at>

Hi Max,

On Thu, Feb 15, 2018 at 1:34 AM, Maximilian Moser
<e1326252@student.tuwien.ac.at> wrote:
> I actually just wanted to get this thesis over with and thought, why not
> post the result to the mailing list
> I'll probably focus more on the written part of the
> thesis, so fixing the issues will probably have to wait a while on my part.

I'm certainly not interested in "throw it over the fence" coding. I'm
happy to work with you on "the acceptance and the possible prospect of
this thing getting packaged for distros," as you wrote, but only if
you're actually committed to maintaining it. It sounds to me like this
is something in your mind that is "over with"? That's disapointing.

> Regarding the issues... About some of them, I did know in one way or the
> other.
> So I'm somewhat excited about the acceptance and the possible prospect of
> this thing getting packaged for distros :D

As I wrote earlier, this is going to require a lot of work to actually
bring to fruition. The first priority should be entirely dispensing
with the use of wg-quick. In order to aid these efforts, I spent some
time writing a mini single-file-c library that you can drop into your
project as a means for talking to the kernel and configuring devices
directly:

https://git.zx2c4.com/WireGuard/tree/contrib/examples/embeddable-wg-library/README

Should be pretty straight-forward to integrate. You'll basically only
need to use the "wg_set_device" function, and perhaps the
"wg_key_from_base64" function too.

Jason

  reply	other threads:[~2018-02-15 14:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 15:05 Max Moser
2018-02-14 15:28 ` Jason A. Donenfeld
2018-02-14 16:58   ` Jordan DeBeer
2018-02-15  0:34     ` Maximilian Moser
2018-02-15 14:07       ` Jason A. Donenfeld [this message]
2018-02-15 14:35         ` Maximilian Moser
2018-02-15 14:46           ` Jason A. Donenfeld
2018-02-15 14:57             ` Maximilian Moser
2018-02-15 20:15               ` Maykel Moya
2018-02-16  5:33                 ` Jason A. Donenfeld
2018-02-16 10:43                   ` Max Moser
2018-02-16 15:07                   ` Manuel Schölling
2018-02-16 21:00                     ` Javier Arteaga
2018-02-14 19:47   ` Daniel Kahn Gillmor

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='CAHmME9rZU8y8mjHhHkVJ9foRW8Wuk5QMoijMfVU=_4LHfg7F-w@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=debee1jp@gmail.com \
    --cc=e1326252@student.tuwien.ac.at \
    --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).