From: Michael Gerlach <n3ph@terminal21.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Rust Version
Date: Wed, 15 Feb 2017 19:25:15 +0100 [thread overview]
Message-ID: <20170215182515.GA9852@c3po> (raw)
In-Reply-To: <3937BCFE-F4EB-4E95-A46E-A87ECA8D9414@icloud.com>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
Hey Sascha,
correct me if I am wrong - I am wondering what DPI should do with a
crypto-stream and what "obfuscating" could improve at this point?
Best regards,
n3ph
On Wed, Feb 15, 2017 at 06:47:36PM +0100, Sascha Grunert wrote:
> Hey WireGuard developers,
>
> I just wanted to know what the current status of the cross platform version of wireguard is and would vote for a Rust implementation.
>
> I am willing to support the development since I have network programming background and know Rust.
>
> Further it would be cool to add obfuscation support to the protocol to make it Deep Packet Inspection (DPI) safe.
>
> Best regards,
> Sascha
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
--
Please use PGP - https://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-02-15 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 17:47 Rust Version Sascha Grunert
2017-02-15 18:25 ` Michael Gerlach [this message]
2017-02-15 18:29 ` Sascha Grunert
2017-02-15 21:40 ` Daniel Kahn Gillmor
2017-02-17 13:38 ` 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=20170215182515.GA9852@c3po \
--to=n3ph@terminal21.de \
--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.