From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2014-04-20
Date: Mon, 21 Apr 2014 22:12:13 +0200 [thread overview]
Message-ID: <20140421221213.0494d4f8@skate> (raw)
In-Reply-To: <39A54937CC95F24AA2F794E2D2B66B1356CB9F10@de02wembxa.internal.synopsys.com>
Dear Anton Kolesov,
On Mon, 21 Apr 2014 13:29:14 +0000, Anton Kolesov wrote:
> Makefile.in of openswan contains -fPIE hardcoded . I suppose that is
> for the "security reasons", because this packages is IPsec
> implementation. I'm not a security expert, so I'm not sure how much
> PIE is important here. I would say that it is not much of the use to
> apply randomization to selected package, while leaving the rest of
> software on the same system without randomization.
Since we don't build all our binaries -fPIE, I don't think it makes
much sense to build just openswan -fPIE. So probably a simple patch to
remove -fPIE from openswan makefiles should be OK.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-21 20:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-20 Thomas Petazzoni
2014-04-21 9:49 ` [Buildroot] Analysis of build " Thomas Petazzoni
2014-04-21 10:18 ` Anton Kolesov
2014-04-21 11:58 ` Thomas Petazzoni
2014-04-21 13:29 ` Anton Kolesov
2014-04-21 20:12 ` Thomas Petazzoni [this message]
2014-04-21 13:47 ` Alexey Brodkin
2014-04-21 20:13 ` Thomas Petazzoni
2014-04-21 14:24 ` Yann E. MORIN
2014-04-21 17:03 ` Eric Le Bihan
2014-04-21 17:17 ` Yann E. MORIN
2014-04-21 17:56 ` Eric Le Bihan
2014-04-21 18:03 ` Yann E. MORIN
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=20140421221213.0494d4f8@skate \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.