From: "dpreed@deepplum.com" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] linus vs wireguard
Date: Thu, 2 Aug 2018 14:50:12 -0400 (EDT) [thread overview]
Message-ID: <1533235812.1032775@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw57zrqugHiu1p0PZyr5ymLC_dy4dDFRDpyW_LwJ7KRhEA@mail.gmail.com>
Please note that my comments are from someone who, unlike Edge Security, has been involved in secure systems design off and on since 1973, not 2003 which is the level of expertise claimed by Edge Security. And I think I am the first person to write an automated system kernel exploit generation tool at about that time, working on the Multics Security Kernel project. The explotss generated searched for cases where the kernel entry points were sensitive to concurrent changes in other processors, just like Spectre and Meltdown exploit concurrent microarchitecture stuff.
This is why putting complexint in the hands of kernel developers who share a single protection domain (the kernel) is REALLY dangerous. It's not a theoretical pedantic issue.
But hey, Linus doesn't give a shit.
-----Original Message-----
From: "Dave Taht" <dave.taht@gmail.com>
Sent: Thursday, August 2, 2018 2:26pm
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] linus vs wireguard
---------- Forwarded message ---------
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu, Aug 2, 2018 at 11:19 AM
Subject: Re: [GIT] Networking
To: David Miller <davem@davemloft.net>
Cc: Andrew Morton <akpm@linux-foundation.org>, Network Development
<netdev@vger.kernel.org>, Linux Kernel Mailing List
<linux-kernel@vger.kernel.org>
On Wed, Aug 1, 2018 at 9:37 PM David Miller <davem@davemloft.net> wrote:
>
> Fixes keep trickling in:
Pulled.
Btw, on an unrelated issue: I see that Jason actually made the pull
request to have wireguard included in the kernel.
Can I just once again state my love for it and hope it gets merged
soon? Maybe the code isn't perfect, but I've skimmed it, and compared
to the horrors that are OpenVPN and IPSec, it's a work of art.
Linus
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2018-08-02 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180801.213753.1303803168352407122.davem@davemloft.net>
[not found] ` <CA+55aFz5EWE9OTbzDoMfsY2ez04Qv9eg0KQhwKfyJY0vFvoD3g@mail.gmail.com>
2018-08-02 18:26 ` Dave Taht
2018-08-02 18:41 ` dpreed
2018-08-02 18:56 ` Dave Taht
2018-08-02 19:25 ` valdis.kletnieks
2018-08-02 20:08 ` Toke Høiland-Jørgensen
2018-08-02 18:50 ` dpreed [this message]
2018-08-02 19:04 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1533235812.1032775@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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