Bug 954343

Summary: dircproxy package should be built with PIE flags
Product: [Fedora] Fedora Reporter: Dhiru Kholia <dkholia>
Component: dircproxyAssignee: Kevin Fenzi <kevin>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bressers, jarodwilson, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dircproxy-1.2.0-0.18.RC1.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-24 20:49:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dhiru Kholia 2013-04-22 10:47:41 UTC 
Description of problem:

http://fedoraproject.org/wiki/Packaging:Guidelines#PIE says that "you MUST
enable the PIE compiler flags if your package is long running ...".

However, currently dircproxy is not being built with PIE flags. This is a
clear violation of the packaging guidelines.

This issue (in its wider scope) is being discussed at,

https://fedorahosted.org/fesco/ticket/1104

https://lists.fedoraproject.org/pipermail/devel/2013-March/180827.html

Version-Release number of selected component (if applicable):

dircproxy-1.2.0-0.17.RC1.fc19.x86_64.rpm

How reproducible:

You can use following programs to check if a package is hardened:

http://people.redhat.com/sgrubb/files/rpm-chksec

OR

https://github.com/kholia/checksec

Steps to Reproduce:

Get scanner.py from https://github.com/kholia/checksec

$ ./scanner.py dircproxy-1.2.0-0.17.RC1.fc19.x86_64.rpm
dircproxy,dircproxy-1.2.0-0.17.RC1.fc19.x86_64.rpm,/usr/bin/dircproxy,NX=Enabled,CANARY=Enabled,RELRO=Partial,PIE=Disabled,RPATH=Disabled,RUNPATH=Disabled,FORTIFY=Enabled,CATEGORY=network-ip
dircproxy,dircproxy-1.2.0-0.17.RC1.fc19.x86_64.rpm,/usr/bin/dircproxy-crypt,NX=Enabled,CANARY=Enabled,RELRO=Partial,PIE=Disabled,RPATH=Disabled,RUNPATH=Disabled,FORTIFY=Enabled,CATEGORY=None
Comment 1 Fedora Update System 2013-04-22 20:49:20 UTC 
dircproxy-1.2.0-0.18.RC1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/dircproxy-1.2.0-0.18.RC1.fc19
Comment 2 Fedora Update System 2013-04-23 03:03:18 UTC 
Package dircproxy-1.2.0-0.18.RC1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dircproxy-1.2.0-0.18.RC1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-6348/dircproxy-1.2.0-0.18.RC1.fc19
then log in and leave karma (feedback).
Comment 3 Fedora Update System 2013-05-24 20:49:38 UTC 
dircproxy-1.2.0-0.18.RC1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.