From: Roland Hieber <rhi@pengutronix.de>
To: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH 3/5] v7a: enable stack clash protection
Date: Mon, 11 Mar 2019 00:13:30 +0100 [thread overview]
Message-ID: <20190310231330.6akscskzvllsul6b@pengutronix.de> (raw)
In-Reply-To: <20190308105328.20008-3-rhi@pengutronix.de>
Nooo, these need a toolchain version bump because
-fstack-clash-protection is not known to gcc-7. Will send a v2 shortly.
- Roland
On Fri, Mar 08, 2019 at 11:53:26AM +0100, Roland Hieber wrote:
> 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.
>
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> ---
> configs/platform-v7a/platformconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configs/platform-v7a/platformconfig b/configs/platform-v7a/platformconfig
> index afb7c7b..6e44290 100644
> --- a/configs/platform-v7a/platformconfig
> +++ b/configs/platform-v7a/platformconfig
> @@ -80,7 +80,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
--
Roland Hieber | r.hieber@pengutronix.de |
Pengutronix e.K. | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next prev parent reply other threads:[~2019-03-10 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 10:53 [DistroKit] [PATCH 1/5] scripts: add helper to run PTXdist on all platformconfigs Roland Hieber
2019-03-08 10:53 ` [DistroKit] [PATCH 2/5] ptxdist: version bump 2019.02.0 → 2019.03.0 Roland Hieber
2019-03-08 10:53 ` [DistroKit] [PATCH 3/5] v7a: enable stack clash protection Roland Hieber
2019-03-10 23:13 ` Roland Hieber [this message]
2019-03-08 10:53 ` [DistroKit] [PATCH 4/5] rpi: " Roland Hieber
2019-03-08 10:53 ` [DistroKit] [PATCH 5/5] v8a: " Roland Hieber
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=20190310231330.6akscskzvllsul6b@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