All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sascha Grunert <saschagrunert@icloud.com>
To: sopium <sopium@mysterious.site>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Rust implementation status
Date: Sat, 18 Mar 2017 11:51:00 +0100	[thread overview]
Message-ID: <6D082187-55EF-49E0-AF0D-71B648984B14@icloud.com> (raw)
In-Reply-To: <8726b4ef-f654-4be5-8025-865a55187c77@Spark>

Hey Folks,

To make it clear for now: If you want to contribute, simply use GitHub =
issues and pull requests. I will take care of the synchronisation of the =
repositories for now.

It would be really cool if we can focus on merging our efforts and =
planning the next steps via GitHub issues. Discussions via the mailing =
list are very welcome as well.

I merged the first pull request for now. Thank you very much and have a =
nice weekend!

Best regards,
Sascha


> Am 14.03.2017 um 19:49 schrieb Sascha Grunert =
<saschagrunert@icloud.com>:
>=20
> Hey guys,
>=20
> I would really like to do that. For the main development I would throw =
this into discussion: =
https://github.com/WireGuard/wireguard-rs/issues/1#issuecomment-286521908
>=20
> I guess it would be more visible to the Rust community if we allow =
maintaining it via the GitHub repository.
>=20
> @Jason, what do you think?
>=20
> Best regards,
> Sascha
>=20
> Am 14. M=C3=A4rz 2017, 17:29 +0100 schrieb sopium =
<sopium@mysterious.site>:
>> Hi Sascha and folks,
>>=20
>> ---- On Sun, 05 Mar 2017 20:42:00 +0900 Sascha Grunert =
<saschagrunert@icloud.com> wrote ----
>>> Hey folks,
>>>=20
>>> I want to call for participation of the Rust userspace =
implementation of WireGuard. The template for the initial implementation =
was this: https://www.wireguard.io/xplatform/ and can be found here: =
https://git.zx2c4.com/wireguard-rs/.
>>>=20
>>> What works for now:
>>>=20
>>> - A main working executable (`cargo run -- -h`) which parses the =
command line parameters via the `clap` crate
>>> - General debug and tracing support via the `log` crate
>>> - Daemonizing support
>>> - The wireguard library which creates a local socket and waits for =
incoming connections (reference implementation)
>>>=20
>>> [...]
>>=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?
>>=20
>> 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!
>>=20
>> For those not closely following this thread, the project is at:
>>=20
>> https://github.com/sopium/titun/tree/wg
>>=20
>> Regards,
>> Sopium
>>=20
>>=20

  reply	other threads:[~2017-03-18 10:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-05 11:42 Rust implementation status 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
2017-03-14 18:49   ` Sascha Grunert
2017-03-18 10:51     ` Sascha Grunert [this message]
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=6D082187-55EF-49E0-AF0D-71B648984B14@icloud.com \
    --to=saschagrunert@icloud.com \
    --cc=sopium@mysterious.site \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.