Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Sascha Grunert <saschagrunert@icloud.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Working on a Rust implementation, and request for test vectors
Date: Tue, 21 Feb 2017 11:07:10 +0100	[thread overview]
Message-ID: <2A1F92D5-90A4-4105-A764-897ADFF15D1D@icloud.com> (raw)
In-Reply-To: <15a5f481984.f050e1c666041.7938484243662330654@mysterious.site>

Hey sopium,

I also would like to develop a Rust version of wireguard, we should join =
our forces! :)
I had a short look at your implementation and suggest some things:

- If we want to develop an implementation of wireguard we should give it =
an "official touch=E2=80=9C, like
  a wireguard GitHub Organization and some official repo.
- We should consider using tokio for async IO processing, that would =
also mean that we implement
  the noise protocol for tokio.

Best regards,
Sascha

> Am 21.02.2017 um 07:07 schrieb sopium <sopium@mysterious.site>:
>=20
> Hello list and Jason,
>=20
> I'd like to tell you that I have started working on a Rust
> implementation of WireGuard (actually to make my TiTun[0] program
> compatible with WireGuard).
>=20
> I have already implemented the Noise part in noise-rust[1]. It is a
> rewrite of screech, with hopefully better API, documentation, testing
> and overall quality. Issues like [2] and [3] should have been
> solved. I wish noise-rust would be helpful for those who want to
> implement WireGuard (or other Noise based protocols) in Rust.
>=20
> I plan to implement the rest of the WireGuard protocol in the
> following weeks. (Well, no promises.) You are welcome to join the
> effort, of course.
>=20
> Jason, can you generate and provide some test vectors for WireGuard?
> E.g. for the less widely used or less clearly defined primitives, like
> HMAC-BLAKE2s and XChaCha20Poly1305. And for whole handshake and
> transportation sessions. And for cookie reply packet generation. That
> should greatly help ensure interoperability between different =
WireGuard
> implementations.
>=20
> 0. https://github.com/sopium/titun
>=20
> 1. https://github.com/sopium/noise-rust
>=20
> 2. https://github.com/trevp/screech/issues/5
>=20
> 3. =
https://github.com/solidsnack/screech/commit/6d91d075ad2f98f03c807a4719534=
95c720a5696
>=20
> Regards,
> Sopium
>=20
>=20
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2017-02-21 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21  6:07 sopium
2017-02-21 10:07 ` Sascha Grunert [this message]
2017-02-21 10:48   ` Jason A. Donenfeld
2017-02-21 11:14   ` Jason A. Donenfeld

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=2A1F92D5-90A4-4105-A764-897ADFF15D1D@icloud.com \
    --to=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).