From: SK <yandereson@riseup.net>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Technical repercussions of grsecurity removal
Date: Mon, 1 May 2017 16:20:30 +0200 [thread overview]
Message-ID: <29deca69-e059-feaf-a312-b0ae53e9610a@riseup.net> (raw)
In-Reply-To: <20170501135808.GA644@gentoo.org>
There is Subgraph that is going to keep maintaining 4.9.X LTS branch
with grsec & there is minipli[1] that is going to forward 4.9.X LTS
branch with grsec.
Would be great to join forces to keep 4.9.X LTS alive while porting
features upstream.
1.
https://github.com/minipli/linux-unofficial_grsec/tree/linux-4.9.x-unofficial_grsec
On 05/01/2017 03:58 PM, Sven Vermeulen wrote:
> On Mon, May 01, 2017 at 01:28:54PM +0300, Andrew Savchenko wrote:
>>> The obvious step is indeed to stop further *current* development on
>>> hardened-sources.
>> Why not support hardened-sources while corresponding vanilla
>> kernels are still supported? E.g. 4.9 is a longterm branch, so we
>> should be able to keep hardened-sources-4.9* up-to-date with
>> vanilla bugfixes. This will give a nice transition period for
>> hardened users.
> Transition to what exactly?
>
> There is one suggestion that mentions we would join forces with other
> projects "out there" to keep supporting the latest PaX patches. But this
> will require knowledgeable resources with enough time to do the necessary
> support on it.
>
> In my humble opinion, this is an effort which is not to be underestimated.
> Maintaining the upstream-provided patches within Gentoo is already an
> endeavour, and now we're talking about even taking on the patch content
> itself as well.
>
> If we have enough volunteers to do so, then let's do it. At least we can
> then have something for users to look forward to. If not, then the current
> long-term branch is also the latest, and the "transition period" is to allow
> users to move to a perhaps lesser kernel-hardened environment.
>
> Wkr,
> Sven Vermeulen
>
next prev parent reply other threads:[~2017-05-01 14:17 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 [this message]
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=29deca69-e059-feaf-a312-b0ae53e9610a@riseup.net \
--to=yandereson@riseup.net \
--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