Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Sascha Grunert <saschagrunert@icloud.com>
To: Michael Gerlach <n3ph@terminal21.de>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Rust Version
Date: Wed, 15 Feb 2017 19:29:55 +0100	[thread overview]
Message-ID: <94F76D79-1813-49E1-AA25-0CE27B3A460D@icloud.com> (raw)
In-Reply-To: <20170215182515.GA9852@c3po>

Hey n3ph,

The DPI could do a simple classification of the stream which could =
others use within network blocking scenarios. The content should be =
safe, but with obfuscation or maybe tor support it would be even =
=E2=80=9EWhisle blower safe=E2=80=9C.

Best regards,
Sascha

> Am 15.02.2017 um 19:25 schrieb Michael Gerlach <n3ph@terminal21.de>:
>=20
> Hey Sascha,
>=20
> 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?
>=20
> Best regards,
>=20
>=20
> n3ph
>=20
> On Wed, Feb 15, 2017 at 06:47:36PM +0100, Sascha Grunert wrote:
>> Hey WireGuard developers,
>>=20
>> I just wanted to know what the current status of the cross platform =
version of wireguard is and would vote for a Rust implementation.
>>=20
>> I am willing to support the development since I have network =
programming background and know Rust.
>>=20
>> Further it would be cool to add obfuscation support to the protocol =
to make it Deep Packet Inspection (DPI) safe.=20
>>=20
>> Best regards,
>> Sascha
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>=20
> --=20
> Please use PGP - https://en.wikipedia.org/wiki/Pretty_Good_Privacy
>=20
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2017-02-15 18:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 17:47 Sascha Grunert
2017-02-15 18:25 ` Michael Gerlach
2017-02-15 18:29   ` Sascha Grunert [this message]
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=94F76D79-1813-49E1-AA25-0CE27B3A460D@icloud.com \
    --to=saschagrunert@icloud.com \
    --cc=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 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).