From: Luiz Angelo Daros de Luca <luizluca@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
Brian Candler <b.candler@pobox.com>
Subject: Re: Reflections on WireGuard Design Goals
Date: Sat, 11 Aug 2018 19:52:07 -0300 [thread overview]
Message-ID: <CAJq09z5GX4QxqhN7j4UC+2cM=fp4FKpZm1gsyREy1f_vhXGzyg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pQJ4-1AGGUd63Nsys2_5tVxecH2rWqVScWdMgNyG_zOA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
> 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
[-- Attachment #2: Type: text/html, Size: 892 bytes --]
next prev parent reply other threads:[~2018-08-11 22:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1318.1533866648.2201.wireguard@lists.zx2c4.com>
2018-08-10 13:35 ` Reflections on WireGuard Design Goals Brian Candler
2018-08-10 14:09 ` Matthias Urlichs
2018-08-10 14:09 ` Kalin KOZHUHAROV
2018-08-10 14:42 ` Eisfunke
2018-08-10 14:47 ` Konstantin Ryabitsev
2018-08-10 15:03 ` Roman Mamedov
2018-08-10 16:03 ` Brian Candler
2018-08-10 16:38 ` Kalin KOZHUHAROV
2018-08-10 16:40 ` jungle Boogie
2018-08-10 17:12 ` Aaron Jones
2018-08-10 17:25 ` jungle Boogie
2018-08-10 20:15 ` em12345
2018-08-10 23:07 ` Reuben Martin
2018-08-11 19:18 ` Jason A. Donenfeld
2018-08-11 22:52 ` Luiz Angelo Daros de Luca [this message]
2018-08-12 0:15 ` Aaron Jones
2018-08-12 0:46 ` Jason A. Donenfeld
2018-08-12 1:07 ` Aaron Jones
2018-08-09 21:52 Jason A. Donenfeld
2018-08-10 15:19 ` nicolas prochazka
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='CAJq09z5GX4QxqhN7j4UC+2cM=fp4FKpZm1gsyREy1f_vhXGzyg@mail.gmail.com' \
--to=luizluca@gmail.com \
--cc=Jason@zx2c4.com \
--cc=b.candler@pobox.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).