public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Zaman <jason@perfinion.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Regarding the State of PaX in the tree
Date: Tue, 17 Apr 2018 02:16:24 +0800	[thread overview]
Message-ID: <20180416181624.GA7717@baraddur.perfinion.com> (raw)
In-Reply-To: <66eafbbf-0198-0946-6437-02e0c5dd9bf9@gentoo.org>

On Mon, Apr 16, 2018 at 07:53:07PM +0200, Toralf Förster wrote:
> On 04/16/2018 11:14 AM, Hanno Böck wrote:
> > There's also another question related to this: What's the future for
> > Gentoo hardened?
> > From what I can tell hardened consists of:
> > * the things that try to make it compatible with grsec/pax
> >   (more or less obsolete).
> > * things that are now in default profiles anyway (aslr, stack
> >   protector).
> > * things that probably should be in default profiles (relro, now linker
> >   flags)
> > * -fstack-check, which should eventually be replaced with
> >   -fstack-clash-protection (only available in future gcc's) and that
> >   should probably also go into default profiles.
> > * Furthermore hardened disables some useful features due to their
> >   incompatibility with pax (e.g. sanitizers).
> 
> Which let me wonder, what I would lose today by a switch from
> 17.0-hardened + USE-flags to 17.0/desktop/plasma at my KDE desktop?

Right now, the main things you'd lose are bindnow and
fstack-protector-all vs fstack-protector-strong i think. But in the
future as new hardening stuff is added to the toolchains they will
likely be enabled in hardened before default too.

-- Jason
> 
> -- 
> Toralf
> PGP 23217DA7 9B888F45
> 
> 





      reply	other threads:[~2018-04-16 18:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16  0:04 [gentoo-dev] Regarding the State of PaX in the tree Anthony G. Basile
2018-04-16  1:25 ` R0b0t1
2018-04-16  2:25 ` Sam Jorna
2018-04-16  6:06 ` Michał Górny
2018-04-16  7:22   ` Ulrich Mueller
2018-04-16 12:20     ` Anthony G. Basile
2018-04-16  8:05 ` Marc Schiffbauer
2018-04-16 12:12   ` Anthony G. Basile
2018-04-16 17:11     ` Patrick McLean
2018-04-19 12:05     ` Marc Schiffbauer
2018-04-16  9:14 ` Hanno Böck
2018-04-16 12:31   ` Anthony G. Basile
2018-04-16 14:26     ` Francesco Riosa
2018-04-16 17:53   ` Toralf Förster
2018-04-16 18:16     ` Jason Zaman [this message]

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=20180416181624.GA7717@baraddur.perfinion.com \
    --to=jason@perfinion.com \
    --cc=gentoo-dev@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