DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [DistroKit] [PATCH v2 11/12] v8a: enable gcc stack clash protection
Date: Mon, 11 Mar 2019 00:40:44 +0100	[thread overview]
Message-ID: <20190310234045.29600-12-rhi@pengutronix.de> (raw)
In-Reply-To: <20190310234045.29600-1-rhi@pengutronix.de>

This setting was introduced in PTXdist 2019.03.0:

    Generate code to prevent stack clash style attacks. When this
    option is enabled, the compiler will only allocate one page of
    stack space at a time and each page is accessed immediately after
    allocation. Thus, it prevents allocations from jumping over any
    stack guard page provided by the operating system.

Make use of it to get more secure binaries with gcc-8's new
-fstack-clash-protection option.

Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
 configs/platform-v8a/platformconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configs/platform-v8a/platformconfig b/configs/platform-v8a/platformconfig
index 711e261..0755c55 100644
--- a/configs/platform-v8a/platformconfig
+++ b/configs/platform-v8a/platformconfig
@@ -78,7 +78,7 @@ PTXCONF_COMPILER_PREFIX_BOOTLOADER="${PTXCONF_COMPILER_PREFIX}"
 PTXCONF_TARGET_HARDEN_STACK=y
 # PTXCONF_TARGET_HARDEN_STACK_STRONG is not set
 # PTXCONF_TARGET_HARDEN_STACK_ALL is not set
-# PTXCONF_TARGET_HARDEN_STACKCLASH is not set
+PTXCONF_TARGET_HARDEN_STACKCLASH=y
 PTXCONF_TARGET_HARDEN_FORTIFY=y
 PTXCONF_TARGET_HARDEN_RELRO=y
 PTXCONF_TARGET_HARDEN_BINDNOW=y
-- 
2.20.1


_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de

  parent reply	other threads:[~2019-03-10 23:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 23:40 [DistroKit] [PATCH v2 00/12] ptxdist and toolchain version bump Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 01/12] gitignore all old config files Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 02/12] scripts: add helper to run PTXdist on all platformconfigs Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 03/12] ptxdist: version bump 2019.02.0 → 2019.03.0 Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 04/12] rpi: toolchain version bump 2018.02 → 2018.12 Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 05/12] rpi: enable gcc stack clash protection Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 06/12] rpi: sync kernelconfig Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 07/12] v7a: toolchain version bump 2018.02 → 2018.12 Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 08/12] v7a: enable gcc stack clash protection Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 09/12] v7a: sync kernelconfig Roland Hieber
2019-03-10 23:40 ` [DistroKit] [PATCH v2 10/12] v8a: toolchain version bump 2018.02 → 2018.12 Roland Hieber
2019-03-10 23:40 ` Roland Hieber [this message]
2019-03-10 23:40 ` [DistroKit] [PATCH v2 12/12] v8a: sync kernelconfig Roland Hieber
2019-03-11  5:51 ` [DistroKit] [PATCH v2 00/12] ptxdist and toolchain version bump Robert Schwebel

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=20190310234045.29600-12-rhi@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    /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