Re: Reflections on WireGuard Design Goals

2018-08-11 Thread Luiz Angelo Daros de Luca
> 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

Re: Reflections on WireGuard Design Goals

2018-08-11 Thread Jason A. Donenfeld
On Fri, Aug 10, 2018 at 6:35 AM Brian Candler wrote: > But I'd feel a lot happier if a second level of authentication were > required to establish a wireguard connection I think that given the WireGuard building block, it's certainly possible to build a 2FA framework around it. And I do

Re: Reflections on WireGuard Design Goals

2018-08-11 Thread Aaron Jones
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/08/18 22:52, Luiz Angelo Daros de Luca wrote: > I see these wireguard extra features just like dhcp is. Nobody > thinks about implementing dhcp inside kernel or even iproute > tools. The Linux kernel has a (minimal, non-configurable) DHCP

Re: Reflections on WireGuard Design Goals

2018-08-11 Thread Jason A. Donenfeld
On Sat, Aug 11, 2018, 17:15 Aaron Jones wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 11/08/18 22:52, Luiz Angelo Daros de Luca wrote: > > I see these wireguard extra features just like dhcp is. Nobody > > thinks about implementing dhcp inside kernel or even iproute > >

Re: Reflections on WireGuard Design Goals

2018-08-11 Thread Aaron Jones
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 12/08/18 00:46, Jason A. Donenfeld wrote: > This is in fact true, but I'm not sure we're planning on following > suite with that kind of thing in kernel space for WireGuard... Indeed. :) -BEGIN PGP SIGNATURE- Comment: Using GnuPG with