From: Greg KH <gregkh@linuxfoundation.org>
To: "Rene 'Renne' Bartsch, B.Sc. Informatics" <ml@bartschnet.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Add Wireguard to Linux staging tree
Date: Tue, 14 May 2019 21:46:58 +0200 [thread overview]
Message-ID: <20190514194658.GB22244@kroah.com> (raw)
In-Reply-To: <9b657152-e9c9-5254-ea3e-0ff4c452fc36@bartschnet.de>
On Tue, May 14, 2019 at 11:11:52AM +0200, Rene 'Renne' Bartsch, B.Sc. Informatics wrote:
> Hi,
>
> it seems activities adding Wireguard to the Linux kernel have stopped
> because of lack of audits and cryptographic weakness tests.
That is not why it has stopped.
> I suggest to offer adding Zinc/Wireguard to the Linux kernel staging
> tree to make it easily available for testing and auditing.
It's easy to test and audit today, adding it to staging is not going to
help that out any, sorry.
thanks,
greg k-h
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-05-14 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 9:11 Rene 'Renne' Bartsch, B.Sc. Informatics
2019-05-14 19:46 ` Greg KH [this message]
2019-05-14 20:18 ` 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=20190514194658.GB22244@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ml@bartschnet.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).