From: Max Moser <e1326252@student.tuwien.ac.at>
To: wireguard@lists.zx2c4.com
Subject: Re: NetworkManager Plugin
Date: Fri, 16 Feb 2018 11:43:14 +0100 [thread overview]
Message-ID: <f9fe4524-b5a1-ce94-4391-ae1fd74099e7@student.tuwien.ac.at> (raw)
In-Reply-To: <CAHmME9oy2uhNfG4vXYHLK2eq36qZA_QWfrTnMrQJWis6sqDTag@mail.gmail.com>
I just read that he's on to something in Rust, don't know any specifics
though.
I've written him an e-mail a couple of days ago, since some sort of
comparison or joining forces may be beneficial for everybody.
On 16/02/18 06:33, Jason A. Donenfeld wrote:
> On Thu, Feb 15, 2018 at 9:15 PM, Maykel Moya <mmoya@mmoya.org> wrote:
>> Wondering about the pic in slide 8 of
>> https://fosdem.org/2018/schedule/event/bulletinboard_dht/attachments/slides/2204/export/events/attachments/bulletinboard_dht/slides/2204/presentation.pdf
> I think he's working on some wilder plugin that incorporates his DHT
> stuff, which is a separate effort from Max's. My personal preference
> is getting a lightweight but functional NetworkManager plugin out
> there for users, that doesn't come with the baggage or bells&whistles
> of the DHT. But for people using the DHT work, having the plugin for
> that is undoubtedly useful.
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-02-16 10:36 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
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 [this message]
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=f9fe4524-b5a1-ce94-4391-ae1fd74099e7@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).