Description of problem: During a security review of Fedora 32, I found that db_dump185 (and possibly other utilities) are not compiled with the PIE flags. It can be checked like this: # annocheck -v --verbose --skip-cf-protection --skip-stack-realign --section-size=.gnu.build.attributes /usr/bin/db_dump185 | grep -i fail Hardened: /usr/bin/db_dump185: FAIL: (addr range: 0x4017f0..0x4017f5): -D_FORTIFY_SOURCE missing from command line. Hardened: /usr/bin/db_dump185: FAIL: Not linked with -Wl,-z,now. Hardened: /usr/bin/db_dump185: FAIL: Some parts of the binary were not compiled with -D_FORTIFY_SOURCE=2. Hardened: /usr/bin/db_dump185: FAIL: Not linked as a position independent executable (ie need to add '-pie' to link command line). Version-Release number of selected component (if applicable): libdb-utils-5.3.28-40.fc32
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 EOL if it remains open with a Fedora 'version' of '32'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 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 this bug is closed as described in the policy above. 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.
The issue is still present on Fedora 33: # dnf install -y /usr/bin/db_dump185 /usr/bin/annocheck # annocheck -v --verbose --skip-cf-protection --skip-stack-realign --section-size=.gnu.build.attributes /usr/bin/db_dump185 | grep -i fail Hardened: /usr/bin/db_dump185: FAIL: pie test because not built with '-Wl,-pie' (gcc/clang) or '-buildmode pie' (go) (source: ELF header) Hardened: /usr/bin/db_dump185: FAIL: bind-now test because not linked with -Wl,-z,now (source: dynamic section) Hardened: /usr/bin/db_dump185: FAIL: stack-prot test because stack protection deliberately disabled (addr range: 0x402570..0x402575) (source: annobin notes) Hardened: /usr/bin/db_dump185: FAIL: fortify test because -D_FORTIFY_SOURCE=2 was not present on command line (addr range: 0x402570..0x402575) (source: annobin notes)
The issue is still present on Fedora 34 with libdb-utils-5.3.28-46.fc34.x86_64.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 EOL if it remains open with a Fedora 'version' of '33'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 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 this bug is closed as described in the policy above. 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.
Still not fixed on F34.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
The issue is still present on Fedora 35 with libdb-utils-5.3.28-49.fc34.x86_64.
And it's present on F36. I think you just need to fix the link on line 271 to include $RPM_LD_FLAGS. This also needs to be copied into LDFLAGS when building the db.1.85 directory.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
Still not fixed in F38.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
FEDORA-2024-d80b485a57 (libdb-5.3.28-62.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-d80b485a57
FEDORA-2024-d80b485a57 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-d80b485a57` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-d80b485a57 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-d80b485a57 (libdb-5.3.28-62.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.