From: "Max Zettlmeißl" <max@zettlmeissl.de>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Current kernel status
Date: Fri, 7 Sep 2018 06:44:58 +0200 [thread overview]
Message-ID: <CACjvM=dOgpwo-q9bhkgK-fGP_crL6TD+tAdnu0Nocws3FPiP1g@mail.gmail.com> (raw)
In-Reply-To: <A4FC0D0B-CC36-4E05-9FFB-3D710068FA6A@gcs-ventures.com>
On Sun, Sep 2, 2018 at 2:25 PM, Guillaume Ceccarelli
<guillaume@gcs-ventures.com> wrote:
> As far as I know, official grsecurity is the only game in town now. I can’t comment on their pricing for personal use. You might want to get in touch and ask them if you haven’t done so recently.
They currently do not offer a program with "a suitable pricing for
personal use" but also state that they are "exploring alternatives".
(Whatever both those things mean exactly.)
In the meantime they suggest to use "minipli's 4.9 unofficial fork",
which is not an attractive option for me.
For the time I stick with the upstream kernel and hope that they
finally start caring more about security. The Kernel Self Protection
Project might be a start, but I doubt that it will be able to change
the current policy when it comes to features which potentially reduce
the general usability of the kernel.
next prev parent reply other threads:[~2018-09-07 4:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 0:33 [gentoo-hardened] Current kernel status Ren Nyo
2018-04-14 12:38 ` Guillaume Ceccarelli
2018-09-02 8:42 ` Alex Efros
2018-09-02 12:25 ` Guillaume Ceccarelli
2018-09-07 4:44 ` Max Zettlmeißl [this message]
2018-09-02 20:39 ` Ren Nyo
2018-09-03 10:03 ` philipp.ammann
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='CACjvM=dOgpwo-q9bhkgK-fGP_crL6TD+tAdnu0Nocws3FPiP1g@mail.gmail.com' \
--to=max@zettlmeissl.de \
--cc=gentoo-hardened@lists.gentoo.org \
/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