From: Rik van Riel <riel@redhat.com>
To: Mathias Krause <minipli@googlemail.com>,
Kees Cook <keescook@chromium.org>
Cc: "Daniel Cegiełka" <daniel.cegielka@gmail.com>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: Re: [kernel-hardening] It looks like there will be no more public versions of PaX and Grsec.
Date: Mon, 01 May 2017 20:09:05 -0400 [thread overview]
Message-ID: <1493683745.2530.2.camel@redhat.com> (raw)
In-Reply-To: <CA+rthh-CO287OpGun1-zYc-V632jSHRuwp=Hm0cAnbo1waJKsw@mail.gmail.com>
On Tue, 2017-05-02 at 00:01 +0200, Mathias Krause wrote:
> I think the intention of the KSPP is good -- making vanilla Linux
> more
> secure. But the way it does its work harms overall Linux security. It
> does hurt mine, that's for sure!
Yeah, no. The grsecurity people produced patches
that were used on maybe a few tens of thousands
of systems, while the KSPP code will end up
enhancing the security of over a billion Android
devices.
Those Android devices are more likely to require
hardening, too, since they do not receive security
updates as quickly as the systems maintained by
grsecurity users.
Integrating hardening into the upstream kernel is
a good thing for security, not a bad thing.
next prev parent reply other threads:[~2017-05-02 0:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 21:05 [kernel-hardening] It looks like there will be no more public versions of PaX and Grsec Daniel Cegiełka
2017-04-26 22:04 ` Kees Cook
2017-05-01 22:01 ` Mathias Krause
2017-05-02 0:09 ` Rik van Riel [this message]
2017-05-02 14:46 ` Shawn
2017-05-02 18:55 ` Kees Cook
2017-05-03 4:50 ` Shawn
2017-05-03 18:56 ` Rik van Riel
2017-05-03 19:36 ` Daniel Micay
2017-05-04 5:45 ` Kees Cook
2017-05-04 6:47 ` Lionel Debroux
2017-05-05 19:54 ` Kees Cook
2017-05-04 14:11 ` Shawn
2017-05-04 16:03 ` Greg KH
2017-05-04 17:12 ` Shawn
2017-05-04 17:23 ` Greg KH
2017-05-02 21:16 ` Mathias Krause
2017-05-02 21:50 ` Casey Schaufler
2017-05-02 22:57 ` Kees Cook
2017-05-03 19:02 ` Rik van Riel
2017-05-03 19:27 ` Daniel Micay
2017-05-02 0:39 ` Olof Johansson
2017-05-02 0:44 ` Casey Schaufler
2017-05-02 0:54 ` Kees Cook
2017-05-11 1:24 ` PaX Team
2017-05-11 16:30 ` Daniel Micay
2017-05-11 18:02 ` Kees Cook
2017-05-12 11:34 ` Hunger
2017-07-31 13:38 ` Solar Designer
2017-05-02 11:11 ` David Gens
2017-05-02 21:27 ` Mathias Krause
2017-05-03 8:59 ` David Gens
2017-05-03 19:10 ` Rik van Riel
[not found] <1788778362.1495506.1493751985632.ref@mail.yahoo.com>
2017-05-02 19:06 ` Lionel Debroux
2017-05-02 22:35 ` Kees Cook
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=1493683745.2530.2.camel@redhat.com \
--to=riel@redhat.com \
--cc=daniel.cegielka@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=minipli@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.