From: Luis Ressel <aranea@aixah.de>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] RIP hardened-sources
Date: Sat, 29 Apr 2017 19:04:26 +0200 [thread overview]
Message-ID: <20170429190426.5b8e6bb0@gentp.lnet> (raw)
In-Reply-To: <CAPLrYETZWnKoxpaA41BfXMOePZmX_T9ne0yjMpAFgBY=PH5LtA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
On Sat, 29 Apr 2017 17:56:10 +0200
Daniel Cegiełka <daniel.cegielka@gmail.com> wrote:
> By the way, I don't know what the Gentoo Hardened or Alpine Linux
> have done wrong, that now are left out in the cold.
That's the part I don't get either. Since the only possible motivation
I can think of for this move is to generate more income, they could've
at least tried asking the community for donations first.
Now, I suppose someone is going to answer "If you'd be willing do
regularily donate to them, you might as well get a subscription", but I
fear this might have some serious drawbacks. In the past years,
the Gentoo Hardened devs have invested quite some work to make sure
most applications in the tree work on grsec/PaX-enabled kernels without
too much fallout. But now, there's suddently a lot less motivation to
keep up this work.
> Instead of complaining, we have to decide what to do next. In my
> opinion, it is critical to maintain support for PaX* for future
> kernels. It will not be easy, so I'm right away saying that Gentoo
> Hardened, Alpine Linux etc. should join forces in realizing this
> project. I think there will be more people who will be interested
> in...
It might be hard to come up with the manpower needed to maintain such a
large kernel patch. Assuming upstream stand by their decision in
the long run, I think the only reasonable long-term approach would be to
try mainlining as much as possible and forget about the rest. And as
Brad and PaX Team can surely tell us, that'd be a gargantuan task if it
is at all possible.
Regards,
Luis
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-29 17:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 11:49 [gentoo-hardened] RIP hardened-sources Luis Ressel
2017-04-29 12:47 ` Alex Efros
2017-04-29 15:56 ` Daniel Cegiełka
2017-04-29 16:52 ` Javier Juan Martinez Cabezon
2017-04-29 16:58 ` Luis Ressel
2017-04-30 8:15 ` Javier Juan Martinez Cabezon
2017-04-29 17:04 ` Luis Ressel [this message]
2017-04-29 18:43 ` Daniel Cegiełka
2017-04-29 20:34 ` "Tóth Attila"
2017-04-29 22:04 ` Brant Williams
2017-04-30 13:00 ` Andrew Savchenko
2017-04-30 13:16 ` Alex Efros
2017-04-30 14:34 ` Andrew Savchenko
2017-04-30 14:56 ` "Tóth Attila"
2017-04-30 13:07 ` Andrew Savchenko
2017-04-29 13:11 ` Alex Efros
2017-04-29 13:46 ` PaX Team
2017-04-29 16:46 ` Alex Efros
2017-04-30 11:08 ` Alex Efros
2017-04-30 11:50 ` SK
2017-04-30 11:55 ` SK
2017-04-30 12:32 ` Andrew Savchenko
2017-04-30 12:56 ` Alex Efros
2017-04-30 13:28 ` Andrew Savchenko
2017-04-30 13:07 ` Daniel Cegiełka
2017-04-29 15:30 ` Paweł Hajdan, Jr.
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=20170429190426.5b8e6bb0@gentp.lnet \
--to=aranea@aixah.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