From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Subject: [gentoo-hardened] Technical repercussions of grsecurity removal
Date: Mon, 1 May 2017 09:38:43 +0000 [thread overview]
Message-ID: <20170501093843.GA927@gentoo.org> (raw)
Hi all,
There is a nice debate ongoing on the mailinglist [1] on the topic of
grsecurity's recent decision to no longer provide the test patches to the
public. I'd like to keep the debate on the rationale of it in that
discussion, but focus here on what we, from Gentoo Hardened, now need to do
or which direction we're going to move forward with.
[1]
https://archives.gentoo.org/gentoo-hardened/message/a06145056b167f52c079bffd9c9a51ac
The obvious step is indeed to stop further *current* development on
hardened-sources. I don't know how many additional patchsets are being
implemented in it (blueness? Zorry?) so I don't know if it means that
hardened-sources in total is done with or not.
From the online discussions I also hear that we shouldn't be referring to
grsecurity anymore (even when it was still the test patches). This means
that we need to update our wiki articles, as well as include a note that the
document is only valid until a certain time (I don't want to remove them,
for those users that still have older versions running and want to find the
documentation on it).
Now, I mentioned *current* development. Are there other improvements that we
can look at which make sense to put into hardened-sources, and are there
volunteers to help out with it?
Wkr,
Sven Vermeulen
next reply other threads:[~2017-05-01 9:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 9:38 Sven Vermeulen [this message]
2017-05-01 9:50 ` [gentoo-hardened] Technical repercussions of grsecurity removal 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
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=20170501093843.GA927@gentoo.org \
--to=swift@gentoo.org \
--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