checksec: polkitd 1024 Partial RELRO Canary found NX enabled No PIE * no "FULL RELRO" * no PIE polkitd is a long living process running even as root __________________________________________________ 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.
Thanks for your report. The F19 build is hardened; I'm currently planning to fix F18 only in conjunction with another necessary polkit change, if any, to minimize the testing/packaging effort.
if it would be a low-privileged process i would say "who cares, fine, thanks" but in context that it is running as root and what polkitd is supposed to do i am not really happy
(In reply to Harald Reindl from comment #2) > if it would be a low-privileged process i would say "who cares, fine, > thanks" but in context that it is running as root and what polkitd is > supposed to do i am not really happy Yeah; I understand that this should be fixed, and I'm not terribly happy about this myself, but at least before Flock I just can't devote the necessary time.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.