From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Vladimir Matveev <dpx.infinity@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Rust implementation status
Date: Wed, 15 Mar 2017 10:03:33 -0700 [thread overview]
Message-ID: <CAHmME9oA0b1cB9hx9tnaTUQG+8ADBNJDADnhjmxTpmXtMKtvmQ@mail.gmail.com> (raw)
In-Reply-To: <1489596675.18476.2.camel@gmail.com>
On Wed, Mar 15, 2017 at 9:51 AM, Vladimir Matveev
<dpx.infinity@gmail.com> wrote:
> anything, I do agree with the goal of making Wireguard implementations
> as slim as possible (i.e. following the guideline on https://www.wiregu
> ard.io/xplatform/). My thoughts in this paragraph were about the
> agree that it is right. I was talking about unofficial implementations
> - I don't believe it is possible to force someone not to create a
> Wireguard implementation with a different interface,
Oh, okay, I understand now. Indeed "non-official" ports become harder
to keep consistent. For that reason, I'm actively soliciting
contributions to the main project organization, so we can work
together to get something unified, so that there aren't ugly
fractures.
> Yes, I do agree with this, and I saw your answer on Github already and
> I'm really glad that you are not against this approach.
Cool.
> I'm very sorry if I said something which made you think so.
It's okay, and no need for apology. I was just wondering what was
happening here.
next prev parent reply other threads:[~2017-03-15 17:00 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 [this message]
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
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=CAHmME9oA0b1cB9hx9tnaTUQG+8ADBNJDADnhjmxTpmXtMKtvmQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=dpx.infinity@gmail.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 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.