Bug 1227839

Summary: binutils: ld sporadically generates binaries without relro protection even when told so
Product: Red Hat Enterprise Linux 6 Reporter: Guenther Deschner <gdeschner>
Component: binutilsAssignee: Nick Clifton <nickc>
Status: CLOSED ERRATA QA Contact: Miloš Prchlík <mprchlik>
Severity: medium Docs Contact: Lenka Špačková <lkuprova>
Priority: high    
Version: 6.6CC: arubin, asn, bgollahe, bressers, ebenes, fweimer, gdeschner, hannsj_uhl, jakub, jherrman, jkurik, jrivera, law, mattn, mcermak, mprchlik, nickc, ohudlick, qe-baseos-tools-bugs, sgrubb, tlavigne
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: binutils- Doc Type: Bug Fix
Doc Text:
RELRO protection now properly applied when requested Previously, binary files started by the system loader would, in some cases, lack the Relocation Read-Only (RELRO) protection even though this had been explicitly requested when the application was built. This was due to a miscommunication between the static linker and the system loader. The underlying source code of the linker has been adjusted to ensure that it makes it possible for the loader to apply the RELRO protection, thus restoring the security feature for applications. Applications and all dependent object files, archives, and libraries built with a previous version of _binutils_ should be rebuilt to correct this defect.
Story Points: ---
Clone Of: 1200138 Environment:
Last Closed: 2016-05-10 21:11:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1200138    
Bug Blocks: 1172231, 1189104, 1189204, 1198591, 1201345, 1206541, 1206545, 1209858, 1271375    

Comment 12 Miloš Prchlík 2016-02-08 14:09:40 UTC
Verified for build binutils-

Comment 17 errata-xmlrpc 2016-05-10 21:11:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.