From Fedora Project Wiki
Line 55: Line 55:
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
-->
 
-->
* Tracker bug: <will be assigned by the Wrangler>
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1413529 #1413529]
  
 
== Detailed Description ==
 
== Detailed Description ==

Revision as of 09:45, 16 January 2017


Golang buildmode PIE

Summary

Change default build mode of golang in Fedora packaging macros to buildmode=pie, which results in packages using them to produce Position Independent Executables. Another part of the change is to pass the Fedora hardened linker flags to the external linker(regular system linker). In result reducing exploit-ability of binaries.

Owner

  • Name: Jakub Čajka
  • Email: <jcajka@fedoraproject.org>
  • Release notes owner:

Current status

Detailed Description

Change default build mode of golang in Fedora packaging macros to buildmode=pie, which results in packages using them to produce Position Independent Executables. Another part of the change is to pass the Fedora hardened linker flags to the external linker(regular system linker). This will only affect packages that depend on golang packaging macros for their build. This should be first step towards mandating this on all packages that provide binaries based on golang in whole distribution via Go packaging guidelines(which is out of scope for this change proposal).


Benefit to Fedora

Reducing exploit surface of golang based packages providing binaries.


Scope

  • Proposal owners: change the Go packaging macros, resolve possible issue encountered
  • Other developers: help with resolving any issues encountered
  • Release engineering: none as mass-rebuild is scheduled
  • Policies and guidelines: none
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

none

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: Either backing of the change to macros or changes to affected packages.
  • Contingency deadline: BetaFreeze?
  • Blocks release? No
  • Blocks product? No

Documentation

N/A (not a System Wide Change)

Release Notes