From: Alex Efros <powerman@powerman.name>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] RIP hardened-sources
Date: Sun, 30 Apr 2017 16:16:46 +0300 [thread overview]
Message-ID: <20170430131646.GC11463@home.power> (raw)
In-Reply-To: <20170430160039.95094713c37afa2379ff5551@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]
Hi!
On Sun, Apr 30, 2017 at 04:00:39PM +0300, Andrew Savchenko wrote:
> The only way to preserve this functionality in the long run is to
> port it to the mainline kernel. This will not be easy, most likely
> not everything will be accepted, some stuff will have to be
> reimplemented using another approaches, etc.
We had 16 years to do this with help of GrSec/PaX developers. It wasn't
happened, and it's unlikely happens now unless some huge company decide to
spend a lot of resources for this. Maybe Google will do, in the name of
increasing Android security. And I'm afraid there are no more options now.
> But there is no other way. GrSec/PaX team can be trusted no longer.
> They ruined all 16 years of good and trustworthy record by what was
> done 3 days ago, though the first bells rang 2 years ago when paid
> subscription for stable patches was enforced. Even if they will
> yield to the community pressure now, they may repeat this betrayal
> later and thus can be trusted no longer.
Hey hey hey! Don't be so harsh. No one is perfect, everyone made mistakes,
and credits/money/ego is very usual "good" reason to made mistake.
Not all people is able to admit their mistakes and fix them, but we still
may believe in GrSec/PaX developers. Just give them some time to cool down
and a few good reasons to change their decision. They've pushed the
button, true, but they can also release the button if they will like to.
And tell it was a "training alert". :)
--
WBR, Alex.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-30 13:16 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
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 [this message]
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=20170430131646.GC11463@home.power \
--to=powerman@powerman.name \
--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