Bug 955314 - novacom-server package should be built with PIE flags
Summary: novacom-server package should be built with PIE flags
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: novacom-server
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jonathan Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-22 18:40 UTC by Dhiru Kholia
Modified: 2014-03-25 03:44 UTC (History)
2 users (show)

Fixed In Version: novacom-server-1.1.0-0.10.rc1.fc20
Clone Of:
Environment:
Last Closed: 2014-02-16 23:23:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
this should enable PIE (3.98 KB, text/x-rpm-spec)
2013-04-24 15:53 UTC, Dhiru Kholia
no flags Details

Description Dhiru Kholia 2013-04-22 18:40:53 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 novacom-server 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):

novacom-server-1.1.0-0.8.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 novacom-server-1.1.0-0.8.rc1.fc19.x86_64.rpm
novacom-server,novacom-server-1.1.0-0.8.rc1.fc19.x86_64.rpm,/usr/bin/novacomd,NX=Enabled,CANARY=Enabled,RELRO=Partial,PIE=Disabled,RPATH=Disabled,RUNPATH=Disabled,FORTIFY=Enabled,CATEGORY=network-ip

Comment 1 Jonathan Dieter 2013-04-22 19:04:35 UTC
Ok, now I'm really confused.  I thought I had turned on the hardened build by setting %global _hardened_build 1 in the spec, but at least according to rpm-chksec, it still doesn't have PIE enabled.  I've even tried manually adding -fPIE, but it seems to be having no effect.  Do you have any idea what I'm doing wrong?

Comment 2 Dhiru Kholia 2013-04-24 15:53:28 UTC
Created attachment 739512 [details]
this should enable PIE

Comment 3 Dhiru Kholia 2013-04-24 18:31:36 UTC
Using " %{?__global_ldflags}" should be better (at least that is what I was told).

Before using the attached patched .spec file, I would recommend getting it reviewed.

Comment 4 Dhiru Kholia 2013-05-17 03:27:22 UTC
Jonathan,

Does the attached patched .spec file works?

Comment 5 Fedora Update System 2014-01-24 08:50:58 UTC
novacom-server-1.1.0-0.10.rc1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/novacom-server-1.1.0-0.10.rc1.fc20

Comment 6 Fedora Update System 2014-01-24 08:52:44 UTC
novacom-server-1.1.0-0.10.rc1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/novacom-server-1.1.0-0.10.rc1.fc19

Comment 7 Fedora Update System 2014-01-25 02:17:11 UTC
Package novacom-server-1.1.0-0.10.rc1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing novacom-server-1.1.0-0.10.rc1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-1456/novacom-server-1.1.0-0.10.rc1.fc20
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2014-02-16 23:23:50 UTC
novacom-server-1.1.0-0.10.rc1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2014-02-16 23:24:16 UTC
novacom-server-1.1.0-0.10.rc1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.