Bug 955221

Summary: voms package should be built with PIE flags
Product: [Fedora] Fedora Reporter: Dhiru Kholia <dkholia>
Component: vomsAssignee: Mattias Ellert <mattias.ellert>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bressers, mattias.ellert, rocha.porto, steve.traylen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: voms-2.0.10-3.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-18 00:33:32 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 14:56:46 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 voms 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):

voms-server-2.0.10-1.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 voms-server-2.0.10-1.fc19.x86_64.rpm
voms-server,voms-server-2.0.10-1.fc19.x86_64.rpm,/usr/sbin/voms,NX=Enabled,CANARY=Enabled,RELRO=Partial,PIE=Disabled,RPATH=Disabled,RUNPATH=Disabled,FORTIFY=Enabled,CATEGORY=network-ip
Comment 1 Dhiru Kholia 2013-05-17 05:17:51 UTC 
Mattias,

Any progress on this bug?
Comment 2 Dhiru Kholia 2013-06-03 06:11:50 UTC 
Do you want me to send a patch for this?
Comment 3 Fedora Update System 2013-08-08 12:49:02 UTC 
voms-2.0.10-3.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/voms-2.0.10-3.fc18
Comment 4 Fedora Update System 2013-08-08 12:49:14 UTC 
voms-2.0.10-3.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/voms-2.0.10-3.el5
Comment 5 Fedora Update System 2013-08-08 12:49:23 UTC 
voms-2.0.10-3.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/voms-2.0.10-3.fc19
Comment 6 Fedora Update System 2013-08-08 12:49:31 UTC 
voms-2.0.10-3.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/voms-2.0.10-3.el6
Comment 7 Fedora Update System 2013-08-09 17:00:03 UTC 
Package voms-2.0.10-3.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 voms-2.0.10-3.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-14456/voms-2.0.10-3.fc19
then log in and leave karma (feedback).
Comment 8 Fedora Update System 2013-08-18 00:33:32 UTC 
voms-2.0.10-3.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 9 Fedora Update System 2013-08-18 00:36:24 UTC 
voms-2.0.10-3.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 10 Fedora Update System 2013-08-31 19:17:17 UTC 
voms-2.0.10-3.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 11 Fedora Update System 2013-08-31 19:19:50 UTC 
voms-2.0.10-3.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.