From: Alexander Kanavin <alex.kanavin@gmail.com>
To: bkylerussell@gmail.com
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] security_flags.inc: don't default to PIE if image-prelink is enabled
Date: Thu, 20 Jan 2022 09:30:56 +0100 [thread overview]
Message-ID: <CANNYZj9TtSZmzNJ8Jjsoa86WUEzKcBgMMEn2=OBrwyYj+dmxQg@mail.gmail.com> (raw)
In-Reply-To: <20220120033045.1098738-1-bkylerussell@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]
I think we pretty much abandoned prelink at this point, are you using it
and do you see the benefits?
Alex
On Thu, 20 Jan 2022 at 04:30, <bkylerussell@gmail.com> wrote:
> Since a prelinked rootfs is in conflict with PIE, don't attempt the latter
> if the image enables prelink.
> ---
> meta/conf/distro/include/security_flags.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/conf/distro/include/security_flags.inc
> b/meta/conf/distro/include/security_flags.inc
> index e469eadca1..be6feb9e5f 100644
> --- a/meta/conf/distro/include/security_flags.inc
> +++ b/meta/conf/distro/include/security_flags.inc
> @@ -5,7 +5,7 @@
> # From a Yocto Project perspective, this file is included and tested
> # in the DISTRO="poky" configuration.
>
> -GCCPIE ?= "--enable-default-pie"
> +GCCPIE ?= "${@bb.utils.contains('USER_CLASSES', 'image-prelink',
> '--disable-default-pie', '--enable-default-pie', d)}"
> # If static PIE is known to work well, GLIBCPIE="--enable-static-pie" can
> be set
>
> # _FORTIFY_SOURCE requires -O1 or higher, so disable in debug builds as
> they use
> --
> 2.25.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#160749):
> https://lists.openembedded.org/g/openembedded-core/message/160749
> Mute This Topic: https://lists.openembedded.org/mt/88551948/1686489
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
[-- Attachment #2: Type: text/html, Size: 2516 bytes --]
next prev parent reply other threads:[~2022-01-20 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 3:30 [PATCH] security_flags.inc: don't default to PIE if image-prelink is enabled Kyle Russell
2022-01-20 8:30 ` Alexander Kanavin [this message]
2022-01-20 17:41 ` [OE-core] " Kyle Russell
2022-01-20 20:43 ` Richard Purdie
2022-01-20 20:51 ` Peter Kjellerstedt
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='CANNYZj9TtSZmzNJ8Jjsoa86WUEzKcBgMMEn2=OBrwyYj+dmxQg@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=bkylerussell@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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;
as well as URLs for NNTP newsgroup(s).