public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hanno Böck" <hanno@hboeck.de>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Gentoo Hardened and Stack Clash
Date: Thu, 22 Jun 2017 12:30:02 +0200	[thread overview]
Message-ID: <20170622123002.7cb34ab1@pc1> (raw)
In-Reply-To: <1fd570dd-1d71-2e3b-2998-cb79a09351a9@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]

Hi,

I'm not claiming that I understand all the issues, but I wonder how
that all affects "normal" Gentoo.

Let me summarize my understanding:
* We currently enable -fstack-check=specific on hardened, but not on
  normal Gentoo.
* -fstack-check provides protection against stack clashes, but it is
  not ideal / can sometimes be circumvented. However it is expected /
  hoped that future versions of gcc will improve on that and provide a
  better implementation.
* According to gcc's man page I understand that -fstack-check=specific
  is equivalent to -fstack-check and there is also
  -fstack-check=generic, which is considered deprecated.

There's already work underway to push -pie via a new profile to default
gentoo. I wonder: Should -fstack-check be pushed as well?

Open questions I have:
* Are there measurements of the performance overhead of -fstack-check?
* Are there other downsides of -fstack-check? Is it expected that
  enabling it breaks things?

-- 
Hanno Böck
https://hboeck.de/

mail/jabber: hanno@hboeck.de
GPG: FE73757FA60E4E21B937579FA5880072BBB51E42

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-06-22 10:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 12:53 [gentoo-hardened] Gentoo Hardened and Stack Clash Francisco Blas Izquierdo Riera (klondike)
2017-06-22 10:30 ` Hanno Böck [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=20170622123002.7cb34ab1@pc1 \
    --to=hanno@hboeck.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