From: Roland Hieber <rhi@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [DistroKit] [PATCH 2/1] v7a: kernel: enable FORTIFY_SOURCES
Date: Mon, 11 Mar 2019 10:27:13 +0100 [thread overview]
Message-ID: <20190311092714.6672-1-rhi@pengutronix.de> (raw)
In-Reply-To: <20190311072426.14329-1-r.czerwinski@pengutronix.de>
Harden common str/mem functions against buffer overflows.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
The other two platforms support it too :-)
---
configs/platform-v7a/kernelconfig | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/configs/platform-v7a/kernelconfig b/configs/platform-v7a/kernelconfig
index 8cca339..6859bfb 100644
--- a/configs/platform-v7a/kernelconfig
+++ b/configs/platform-v7a/kernelconfig
@@ -2978,7 +2978,7 @@ CONFIG_HAVE_HARDENED_USERCOPY_ALLOCATOR=y
CONFIG_HARDENED_USERCOPY=y
CONFIG_HARDENED_USERCOPY_FALLBACK=y
# CONFIG_HARDENED_USERCOPY_PAGESPAN is not set
-# CONFIG_FORTIFY_SOURCE is not set
+CONFIG_FORTIFY_SOURCE=y
# CONFIG_STATIC_USERMODEHELPER is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_DEFAULT_SECURITY=""
@@ -3355,7 +3355,6 @@ CONFIG_FUNCTION_GRAPH_TRACER=y
# CONFIG_TRACER_SNAPSHOT is not set
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
-# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_STACK_TRACER is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_UPROBE_EVENTS is not set
--
2.20.1
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next prev parent reply other threads:[~2019-03-11 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 7:24 [DistroKit] [PATCH] platform-rpi: " Rouven Czerwinski
2019-03-11 9:15 ` Robert Schwebel
2019-03-11 9:27 ` Roland Hieber [this message]
2019-03-11 9:27 ` [DistroKit] [PATCH 3/1] v8a: kernel: " Roland Hieber
2019-03-11 9:31 ` [DistroKit] [PATCH 2/1] v7a: " Robert Schwebel
2019-03-11 9:40 ` 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=20190311092714.6672-1-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