Development discussion of WireGuard
 help / color / mirror / Atom feed
From: sopium <sopium@mysterious.site>
To: "Sascha Grunert" <saschagrunert@icloud.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Rust implementation status
Date: Wed, 15 Mar 2017 01:29:12 +0900	[thread overview]
Message-ID: <15acda6e9bc.b852f6478142.4195445703657110954@mysterious.site> (raw)
In-Reply-To: <E63B612D-BFAA-48FE-A352-25B4C11B8E05@icloud.com>

Hi Sascha and folks,

 ---- On Sun, 05 Mar 2017 20:42:00 +0900 Sascha Grunert <saschagrunert@iclo=
ud.com> wrote ----=20
 > Hey folks,=20
 > =20
 > I want to call for participation of the Rust userspace implementation of=
 WireGuard. The template for the initial implementation was this: https://w=
ww.wireguard.io/xplatform/ and can be found here: https://git.zx2c4.com/wir=
eguard-rs/.=20
 > =20
 > What works for now:=20
 > =20
 > - A main working executable (`cargo run -- -h`) which parses the command=
 line parameters via the `clap` crate=20
 > - General debug and tracing support via the `log` crate=20
 > - Daemonizing support=20
 > - The wireguard library which creates a local socket and waits for incom=
ing connections (reference implementation)=20
 >
 > [...]

I have kept an eye on this. It seems that you were mostly working
on the `xplatform` stuff, and haven't started on the actual
implementation of the protocol yet. My code has (partly)
implemented the protocol, but lacks the `xplatform` ui. So it
seems like a perfect time to merge efforts. What do you think?

And to all who are interested in userspace WG impls, in
particular Rust impls, I have adjusted the goal of my project to
=E2=80=9Cto write a secure, compatible, cross-platform and reasonably
fast user-space implementation of WireGuard in Rust=E2=80=9D. I am also
committed to finishing and maintaining it. There is a big TODO
list, and contribution is welcome!

For those not closely following this thread, the project is at:

  https://github.com/sopium/titun/tree/wg

Regards,
Sopium

  parent reply	other threads:[~2017-03-14 16:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-05 11:42 Sascha Grunert
2017-03-12 23:09 ` Vladimir Matveev
2017-03-13 16:58   ` Sascha Grunert
2017-03-14 10:11     ` Vladimir Matveev
2017-03-15 15:59       ` Jason A. Donenfeld
2017-03-15 16:51         ` Vladimir Matveev
2017-03-15 17:03           ` Jason A. Donenfeld
2017-03-13  7:04 ` sopium
     [not found]   ` <CAHmME9oFbpNBTszO_Q5m8EwiG0F0SH6BUd+1SFZGUDGH0wQ0gg@mail.gmail.com>
2017-03-13 14:39     ` Jason A. Donenfeld
2017-03-14 13:08       ` sopium
2017-03-14 16:29 ` sopium [this message]
2017-03-14 18:49   ` Sascha Grunert
2017-03-18 10:51     ` Sascha Grunert
2017-03-13 17:00 Sascha Grunert

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=15acda6e9bc.b852f6478142.4195445703657110954@mysterious.site \
    --to=sopium@mysterious.site \
    --cc=saschagrunert@icloud.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).