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 vtun 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): vtun-3.0.3-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 vtun-3.0.3-3.fc19.x86_64.rpm vtun,vtun-3.0.3-3.fc19.x86_64.rpm,/usr/sbin/vtund,NX=Enabled,CANARY=Enabled,RELRO=Partial,PIE=Disabled,RPATH=Disabled,RUNPATH=Disabled,FORTIFY=Enabled,CATEGORY=network-ip
vtun-3.0.3-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/vtun-3.0.3-4.fc19
vtun-3.0.3-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/vtun-3.0.3-4.fc18
Package vtun-3.0.3-4.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 vtun-3.0.3-4.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-7245/vtun-3.0.3-4.fc19 then log in and leave karma (feedback).
Problem has been fixed in haproxy-1.4.23-3.fc19 which is now in stable F19 repository.
Oops. Too many similar bugs. Problem has been fixed in vtun-3.0.3-4.fc19.x86_64.rpm which is now in stable F19 repository.