From: "Daniel Cegiełka" <daniel.cegielka@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Technical repercussions of grsecurity removal
Date: Tue, 2 May 2017 10:28:17 +0200 [thread overview]
Message-ID: <CAPLrYEQ-pBizCyD1nK5KyYOcEZu17UDiQVmMUo9yAWdh7_EeHg@mail.gmail.com> (raw)
In-Reply-To: <bd3abb43-3d61-5593-7fca-3c56fa34bfed@riseup.net>
https://wiki.gentoo.org/wiki/Hardened/Hardened_Kernel_Project
It closes the topic of our discussion.
worth reading:
http://openwall.com/lists/kernel-hardening/2017/05/01/5
http://openwall.com/lists/kernel-hardening/2017/05/02/4
this means:
* KSPP means that keeping PaX for >4.9 will be difficult and painful,
as I pointed out previously
* NSA SELinux instead PAX MPROTECT?
alternatives: RSBAC
* slow, but actively developed:
http://git.rsbac.org/cgi-bin/gitweb.cgi?p=linux-4.9.y.git;a=summary
* produkction ready
* lots of options similar to what is in grsecurity (eg. restricted
chroot in grsec and jail in rsbac):
http://git.rsbac.org/cgi-bin/gitweb.cgi?p=linux-4.9.y.git;a=blob;f=rsbac/Kconfig;h=4a6ae294d41365a5c1757503575074c89ceebb11;hb=HEAD
next prev parent reply other threads:[~2017-05-02 8:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 9:38 [gentoo-hardened] Technical repercussions of grsecurity removal Sven Vermeulen
2017-05-01 9:50 ` Sven Vermeulen
2017-05-01 10:24 ` Daniel Cegiełka
2017-05-01 11:00 ` Andrew Savchenko
2017-05-01 12:25 ` Daniel Cegiełka
2017-05-01 10:28 ` Andrew Savchenko
2017-05-01 13:58 ` Sven Vermeulen
2017-05-01 14:20 ` SK
2017-05-01 14:53 ` Daniel Cegiełka
2017-05-01 15:21 ` SK
2017-05-02 8:28 ` Daniel Cegiełka [this message]
2017-05-08 18:08 ` Miroslav Rovis
2017-05-08 18:57 ` Luis Ressel
2017-05-08 20:07 ` Mathias Krause
2017-05-08 20:49 ` Miroslav Rovis
2017-05-08 23:31 ` Miroslav Rovis
2017-05-09 14:28 ` [gentoo-hardened] Unofficial grsec kernel install WAS: " Miroslav Rovis
2017-05-08 21:12 ` [gentoo-hardened] " Andrew Savchenko
2017-05-12 19:10 ` "Tóth Attila"
2017-05-12 23:38 ` Alex Efros
2017-05-13 0:17 ` Max R.D. Parmer
2017-05-02 15:28 ` Luis Ressel
2017-05-02 15:56 ` Daniel Cegiełka
2017-05-02 16:02 ` Luis Ressel
2017-05-02 16:59 ` Daniel Cegiełka
2017-05-02 17:23 ` "Tóth Attila"
2017-05-02 19:58 ` Daniel Cegiełka
2017-05-02 20:41 ` Alex Efros
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=CAPLrYEQ-pBizCyD1nK5KyYOcEZu17UDiQVmMUo9yAWdh7_EeHg@mail.gmail.com \
--to=daniel.cegielka@gmail.com \
--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