From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: luizluca@gmail.com
Received: from krantz.zx2c4.com (localhost [127.0.0.1])
 by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 090cf10d
 for <wireguard@lists.zx2c4.com>;
 Sat, 11 Aug 2018 22:40:46 +0000 (UTC)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com
 [IPv6:2607:f8b0:4001:c0b::231])
 by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 78f2955c
 for <wireguard@lists.zx2c4.com>;
 Sat, 11 Aug 2018 22:40:45 +0000 (UTC)
Received: by mail-it0-x231.google.com with SMTP id j81-v6so7672167ite.0
 for <wireguard@lists.zx2c4.com>; Sat, 11 Aug 2018 15:52:18 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.1318.1533866648.2201.wireguard@lists.zx2c4.com>
 <b66a15d1-c4f1-78a5-cf5a-4d2a4ca9ce54@pobox.com>
 <CAHmME9pQJ4-1AGGUd63Nsys2_5tVxecH2rWqVScWdMgNyG_zOA@mail.gmail.com>
In-Reply-To: <CAHmME9pQJ4-1AGGUd63Nsys2_5tVxecH2rWqVScWdMgNyG_zOA@mail.gmail.com>
From: Luiz Angelo Daros de Luca <luizluca@gmail.com>
Date: Sat, 11 Aug 2018 19:52:07 -0300
Message-ID: <CAJq09z5GX4QxqhN7j4UC+2cM=fp4FKpZm1gsyREy1f_vhXGzyg@mail.gmail.com>
Subject: Re: Reflections on WireGuard Design Goals
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Content-Type: multipart/alternative; boundary="000000000000520c9e057330b6a8"
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
 Brian Candler <b.candler@pobox.com>
List-Id: Development discussion of WireGuard <wireguard.lists.zx2c4.com>
List-Unsubscribe: <https://lists.zx2c4.com/mailman/options/wireguard>,
 <mailto:wireguard-request@lists.zx2c4.com?subject=unsubscribe>
List-Archive: <http://lists.zx2c4.com/pipermail/wireguard/>
List-Post: <mailto:wireguard@lists.zx2c4.com>
List-Help: <mailto:wireguard-request@lists.zx2c4.com?subject=help>
List-Subscribe: <https://lists.zx2c4.com/mailman/listinfo/wireguard>,
 <mailto:wireguard-request@lists.zx2c4.com?subject=subscribe>

--000000000000520c9e057330b6a8
Content-Type: text/plain; charset="UTF-8"

> I think that given the WireGuard building block, it's certainly
> possible to build a 2FA framework around it.
>

I see these wireguard extra features just like dhcp is. Nobody thinks about
implementing dhcp inside kernel or even iproute tools.

+1 for 2FA and +1 for a service that share peer info, allowing a mesh vpn

> --

Luiz Angelo Daros de Luca
luizluca@gmail.com

--000000000000520c9e057330b6a8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think that =
given the WireGuard building block, it&#39;s certainly<br>
possible to build a 2FA framework around it.=C2=A0<br></blockquote></div><d=
iv><br></div><div>I see these wireguard extra features just like dhcp is. N=
obody thinks about implementing dhcp inside kernel or even iproute tools.</=
div><div><br></div><div>+1 for 2FA and +1 for a service that share peer inf=
o, allowing a mesh vpn</div><div class=3D"gmail_quote"><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
</blockquote></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" data-s=
martmail=3D"gmail_signature"><div dir=3D"ltr"><p dir=3D"ltr">Luiz Angelo Da=
ros de Luca<br>
<a href=3D"mailto:luizluca@gmail.com">luizluca@gmail.com</a></p>
</div></div>

--000000000000520c9e057330b6a8--