Hi Dave,
On Fri, Dec 8, 2017 at 4:38 PM, David Miller wrote:
> Sorry, you cannot force the discussion of a feature which will be submitted
> upstream to occur on a private mailing list.
>
> It is _ABSOLUTELY_ appropriate to discss this on netdev since it is the
> netdev
Hi Dave,
On Fri, Dec 8, 2017 at 4:38 PM, David Miller wrote:
> Sorry, you cannot force the discussion of a feature which will be submitted
> upstream to occur on a private mailing list.
>
> It is _ABSOLUTELY_ appropriate to discss this on netdev since it is the
> netdev community which must
From: "Jason A. Donenfeld"
Date: Fri, 8 Dec 2017 03:17:40 +0100
> On Thu, Dec 7, 2017 at 11:22 AM, Stefan Tatschner
> wrote:
>> I have a question which is related to the involved crypto. As far as I
>> have understood the protocol and the concept of
From: "Jason A. Donenfeld"
Date: Fri, 8 Dec 2017 03:17:40 +0100
> On Thu, Dec 7, 2017 at 11:22 AM, Stefan Tatschner
> wrote:
>> I have a question which is related to the involved crypto. As far as I
>> have understood the protocol and the concept of wireguard
>> What's your opinion on this?
>
On Thu, Dec 7, 2017 at 11:22 AM, Stefan Tatschner
wrote:
> I have a question which is related to the involved crypto. As far as I
> have understood the protocol and the concept of wireguard
> What's your opinion on this?
This thread has been picked up on the WireGuard
On Thu, Dec 7, 2017 at 11:22 AM, Stefan Tatschner
wrote:
> I have a question which is related to the involved crypto. As far as I
> have understood the protocol and the concept of wireguard
> What's your opinion on this?
This thread has been picked up on the WireGuard mailing list, not here.
Hi Jason,
thanks for providing all these information. I am looking forward to
the further development of wireguard!
On Sat, Nov 11, 2017 at 5:48 AM, Jason A. Donenfeld wrote:
> The current biggest blocker is issues with the crypto API. Before WireGuard
> can go upstream, I
Hi Jason,
thanks for providing all these information. I am looking forward to
the further development of wireguard!
On Sat, Nov 11, 2017 at 5:48 AM, Jason A. Donenfeld wrote:
> The current biggest blocker is issues with the crypto API. Before WireGuard
> can go upstream, I intend to embark on a
Hi folks,
This relates to WireGuard [0].
Following a very nice conference with the Linux kernel networking subsystem
community [1,2], I thought it might be a good idea to spell out the roadmap
for the coming months and the trajectory into upstream, based on my
discussions with several developers
Hi folks,
This relates to WireGuard [0].
Following a very nice conference with the Linux kernel networking subsystem
community [1,2], I thought it might be a good idea to spell out the roadmap
for the coming months and the trajectory into upstream, based on my
discussions with several developers
10 matches
Mail list logo