From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Cc: Florian Weimer <fweimer@redhat.com>
Subject: [PATCH 3/8] build: Enable BIND_NOW
Date: Thu, 9 May 2019 14:37:41 +0200 [thread overview]
Message-ID: <20190509123746.8396-3-hadess@hadess.net> (raw)
In-Reply-To: <20190509123746.8396-1-hadess@hadess.net>
From: Florian Weimer <fweimer@redhat.com>
Partial RELRO means that the object is GNU_RELRO but not BIND_NOW. This
reduces the effectiveness of RELRO. bluez triggers this because it
enables PIE during the build, and rpmdiff takes this as an indicator
that the best possible hardening is desired.
https://bugzilla.redhat.com/show_bug.cgi?id=983161
---
acinclude.m4 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/acinclude.m4 b/acinclude.m4
index 7f494cc9d..6ae34b8ae 100644
--- a/acinclude.m4
+++ b/acinclude.m4
@@ -50,7 +50,7 @@ AC_DEFUN([MISC_FLAGS], [
if (test "${enableval}" = "yes" &&
test "${ac_cv_prog_cc_pie}" = "yes"); then
misc_cflags="$misc_cflags -fPIC"
- misc_ldflags="$misc_ldflags -pie"
+ misc_ldflags="$misc_ldflags -pie -Wl,-z,now"
fi
])
if (test "$enable_coverage" = "yes"); then
--
2.21.0
next prev parent reply other threads:[~2019-05-09 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 12:37 [PATCH 1/8] build: Add a few default configure options Bastien Nocera
2019-05-09 12:37 ` [PATCH 2/8] build: Add warnings for non-literal strings Bastien Nocera
2019-05-09 12:37 ` Bastien Nocera [this message]
2019-05-09 12:37 ` [PATCH 4/8] tools/csr_usb: Fix compilation failure Bastien Nocera
2019-05-09 12:37 ` [PATCH 5/8] obex: Work-around " Bastien Nocera
2019-05-09 12:37 ` [PATCH 6/8] android/avrcp-lib: Fix unaligned struct access Bastien Nocera
2019-05-09 12:37 ` [PATCH 7/8] android/hal-bluetooth: " Bastien Nocera
2019-05-09 12:37 ` [PATCH 8/8] android/handsfree: " Bastien Nocera
2019-05-13 17:38 ` [PATCH 1/8] build: Add a few default configure options Luiz Augusto von Dentz
2019-05-13 18:13 ` Bastien Nocera
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=20190509123746.8396-3-hadess@hadess.net \
--to=hadess@hadess.net \
--cc=fweimer@redhat.com \
--cc=linux-bluetooth@vger.kernel.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).