Bug 965522

Summary:	spnavcfg package should be built with PIE flags
Product:	[Fedora] Fedora	Reporter:	Dhiru Kholia <dkholia>
Component:	spnavcfg	Assignee:	Richard Shaw <hobbes1069>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	bressers, hobbes1069, john
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spnavcfg-0.2.1-5.fc19	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-30 02:59:19 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-05-21 10:24:59 UTC

Description of problem:

http://fedoraproject.org/wiki/Packaging:Guidelines#PIE says that "you MUST
enable the PIE compiler flags if your package has suid binaries...".

However, currently spnavcfg 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):

spnavcfg-0.2.1-4.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 spnavcfg-0.2.1-4.fc19.x86_64.rpm
spnavcfg,spnavcfg-0.2.1-4.fc19.x86_64.rpm,/usr/bin/spnavcfg,mode=0104775,NX=Enabled,CANARY=Enabled,RELRO=Partial,PIE=Disabled,RPATH=Disabled,RUNPATH=Disabled,FORTIFY=Enabled,CATEGORY=None

Comment 1 Fedora Update System 2013-05-21 16:12:47 UTC

spnavcfg-0.2.1-5.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/spnavcfg-0.2.1-5.fc19

Comment 2 Fedora Update System 2013-05-21 16:13:02 UTC

spnavcfg-0.2.1-5.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/spnavcfg-0.2.1-5.fc18

Comment 3 Fedora Update System 2013-05-21 16:13:17 UTC

spnavcfg-0.2.1-5.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/spnavcfg-0.2.1-5.fc17

Comment 4 Fedora Update System 2013-05-22 01:22:00 UTC

Package spnavcfg-0.2.1-5.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing spnavcfg-0.2.1-5.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-8786/spnavcfg-0.2.1-5.fc17
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-05-30 02:59:19 UTC

spnavcfg-0.2.1-5.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2013-05-30 03:04:54 UTC

spnavcfg-0.2.1-5.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2013-06-06 02:26:07 UTC

spnavcfg-0.2.1-5.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.