Bug 983602

Summary: no hardened build
Product: [Fedora] Fedora Reporter: Harald Reindl <h.reindl>
Component: fpingAssignee: Charles R. Anderson <cra>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: cra, i
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: fping-3.5-3.fc18 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-21 00:55:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Harald Reindl 2013-07-11 14:26:27 UTC
checksec says:
fping  19738 Partial RELRO     Canary found           NX enabled    No PIE 

http://fedoraproject.org/wiki/Packaging:Guidelines
If your package meets any of the following criteria you MUST enable the PIE compiler flags:
    Your package is long running. This means it's likely to be started and keep running until the machine is rebooted, not start on demand and quit on idle. 
    Your package has suid binaries, or binaries with capabilities. 
    Your package runs as root. 

If your package meets the following criteria you should consider enabling the PIE compiler flags:
    Your package accepts/processes untrusted input.

Comment 1 Harald Reindl 2013-08-13 20:49:39 UTC
any news here?

"you MUST enable the PIE compiler flags if Your package has suid binaries, or binaries with capabilities" is pretty clear

[root@srv-rhsoft:~]$ getcap /usr/sbin/fping
/usr/sbin/fping = cap_net_raw+ep

Comment 3 Harald Reindl 2013-08-14 13:53:15 UTC
as you can see this bugreport is for F18
builds for F19/F20 does not help me much 

http://koji.fedoraproject.org/koji/packageinfo?packageID=1758

Comment 4 Charles R. Anderson 2013-08-14 22:12:01 UTC
Build for F18 in progress now.  People get upset at me if I push to stable Fedora too quickly so don't be surprised if I wait until the package bakes in rawhide for awhile, then push an update to F19, then push an update to F18.

Comment 5 Harald Reindl 2013-08-14 22:18:43 UTC
i understand this, but i am looking at koji at least twice a day and in case of bugreports it is always a good idea if the release the reporter is using get the first koji build because he will most likely be the first tester and using the package in question :-)

Comment 6 Harald Reindl 2013-08-14 23:29:55 UTC
thanls, ymokeping up and running with the new build

rpm -q fping
fping-3.5-3.fc18.x86_64

nobody   21463  0.0  0.0   6384   624 ?        SN   01:27   0:00 /usr/sbin/fping -C 40 -q -B1 -r1 -i10 **.**.**.** **.**.**.** **.**.**.** **.**.**.** **.**.**.**

Comment 7 Fedora Update System 2013-09-01 14:48:13 UTC
fping-3.5-3.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/fping-3.5-3.fc19

Comment 8 Fedora Update System 2013-09-02 23:27:37 UTC
fping-3.5-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-10-04 12:45:01 UTC
fping-3.5-3.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/fping-3.5-3.fc18

Comment 10 Fedora Update System 2013-10-06 01:36:33 UTC
Package fping-3.5-3.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fping-3.5-3.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-18401/fping-3.5-3.fc18
then log in and leave karma (feedback).

Comment 11 Fedora Update System 2013-10-21 00:55:52 UTC
fping-3.5-3.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.