From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] security hardening: add RELFO, FORTIFY options
Date: Mon, 29 Jan 2018 17:48:17 +0100 [thread overview]
Message-ID: <20180129174817.3b964d09@windsurf.lan> (raw)
In-Reply-To: <CANQCQpZY6fS8rojojQx4D3cYWV6ZYWifJoRGZnxiTF3LyWzquw@mail.gmail.com>
Hello,
On Mon, 29 Jan 2018 09:54:16 -0600, Matthew Weber wrote:
> I've internally started to look at build failures across all packages
> with the following config set in an off-line autobuilder.
> BR2_OPTIMIZE_1=y
> BR2_RELRO_FULL=y
> BR2_FORTIFY_SOURCE_1=y
> BR2_SSP_STRONG=y
>
> So far things are pretty broken but we'll see after I get past the tip
> of the iceburg how much work it might take to turn on a basic set of
> these options for regression.
OK, good. At some point, I think we will want to improve our random
config generator to generate once in a while configurations that
include those options.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2018-01-29 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 14:21 [Buildroot] [git commit] security hardening: add RELFO, FORTIFY options Peter Korsgaard
2018-01-29 15:54 ` Matthew Weber
2018-01-29 16:24 ` Peter Korsgaard
2018-01-29 16:48 ` Thomas Petazzoni [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=20180129174817.3b964d09@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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