Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Max Moser <e1326252@student.tuwien.ac.at>
To: wireguard@lists.zx2c4.com
Subject: NetworkManager Plugin
Date: Wed, 14 Feb 2018 16:05:00 +0100	[thread overview]
Message-ID: <7d5325a3-fa07-f67f-a31e-aadd44458d41@student.tuwien.ac.at> (raw)

[-- Attachment #1: Type: text/plain, Size: 1786 bytes --]

Good day, ladies and gentlemen!



I have been working on a NM plugin for wireguard as part of my thesis 
for quite a while, but somehow I've never really found the time to work 
on that (sorry about that!).

*Until recently.*

Since we have semester break in February, I have finally found the time 
(and motivation) to put some effort into this thing.


So, I forked the OpenVPN plugin at some point and built my current 
solution on that foundation. This means that my plugin is actually 
pretty much pure C, so almost no dependencies (obviously, NM, WG and 
GLib stuff).

After briefly talking to my supervisor about making the thing public 
(which he considered to be a pretty positive step), I uploaded it from 
our internal GitLab to GitHub:
https://github.com/max-moser/network-manager-wireguard/ 
<https://github.com/max-moser/network-manager-wireguard/>


The basic workflow of creating a NMConnection (either from scratch 
through the Connection-Editor UI, or by importing a wg-quick formatted 
conf file [export works too]) and connecting to it works.

However, there are still a ton of issues open, of which I'll list just a 
few:

* the plugin sets up the connection by spawning wg-quick on a temporary 
conf file instead of implementing that logic directly
* the Editor UI isn't quite top notch and there are two tabs (IPv4 and 
IPv6) that I did not use, but also can't seem to get rid of
* internally, everything in the plugin is stored as data-item and not as 
secret
* etc.


However, I think that most of those problems are not actually that huge 
and could be fixed without tremendous effort -- they are just many in 
number.

So, if anybody would be interested in checking it out and maybe even 
contributing, I'd be very glad about that! :)



Best regards,

Max


[-- Attachment #2: Type: text/html, Size: 2421 bytes --]

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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 15:05 Max Moser [this message]
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
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=7d5325a3-fa07-f67f-a31e-aadd44458d41@student.tuwien.ac.at \
    --to=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).