Bug 955145

Summary: lighttpd package should be built with PIE flags
Product: [Fedora] Fedora Reporter: Dhiru Kholia <dkholia>
Component: lighttpdAssignee: Gwyn Ciesla <gwync>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bressers, dhiru, matthias
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: lighttpd-1.4.34-3.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-22 18:18:15 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:
Attachments:
Description Flags
this should enable PIE
none
enable PIE (latest patch against rawhide) none

Description Dhiru Kholia 2013-04-22 13:26:03 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 lighttpd 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):

lighttpd-1.4.31-3.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 lighttpd-1.4.31-3.fc19.x86_64.rpm
lighttpd,lighttpd-1.4.31-3.fc19.x86_64.rpm,/usr/sbin/lighttpd,NX=Enabled,CANARY=Enabled,RELRO=Partial,PIE=Disabled,RPATH=Disabled,RUNPATH=Disabled,FORTIFY=Enabled,CATEGORY=network-ip
lighttpd,lighttpd-1.4.31-3.fc19.x86_64.rpm,/usr/sbin/lighttpd-angel,NX=Enabled,CANARY=Disabled,RELRO=Partial,PIE=Disabled,RPATH=Disabled,RUNPATH=Disabled,FORTIFY=NA,CATEGORY=None
Comment 1 Dhiru Kholia 2013-05-14 10:51:40 UTC 
Created attachment 747626 [details]
this should enable PIE
Comment 2 Dhiru Kholia 2013-12-22 05:16:10 UTC 
Created attachment 840260 [details]
enable PIE (latest patch against rawhide)
Comment 3 Dhiru Kholia 2013-12-22 05:17:52 UTC 
Hi Matt,

Can you please test and apply this patch (to enable PIE) ASAP? Thanks!
Comment 4 Fedora Admin XMLRPC Client 2014-02-05 16:31:39 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 5 Fedora Update System 2014-02-12 20:49:52 UTC 
lighttpd-1.4.34-3.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/lighttpd-1.4.34-3.fc20
Comment 6 Fedora Update System 2014-02-12 20:50:27 UTC 
lighttpd-1.4.34-3.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/lighttpd-1.4.34-3.fc19
Comment 7 Fedora Update System 2014-02-14 08:05:18 UTC 
Package lighttpd-1.4.34-3.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 lighttpd-1.4.34-3.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-2495/lighttpd-1.4.34-3.fc20
then log in and leave karma (feedback).
Comment 8 Fedora Update System 2014-02-22 18:18:15 UTC 
lighttpd-1.4.34-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 2014-02-22 18:21:42 UTC 
lighttpd-1.4.34-3.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 10 Red Hat Bugzilla 2023-09-14 01:43:34 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days