Bug 516549
| Summary: | Does libgcrypt need to be blacklisted from prelink? | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tim Waugh <twaugh> |
| Component: | libgcrypt | Assignee: | Tomas Mraz <tmraz> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | jorton, nalin, rdieter, tmraz |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-08-10 12:31:37 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: | |||
|
Description
Tim Waugh
2009-08-10 12:07:31 UTC
The FIPS support in libgcrypt conflicts with prelinking. However the FIPS support is meant only for testing purposes in fedora - the module is not validated in the Fedora. So it does not make much sense to run it in the FIPS mode except for testing. It would not be a good idea to block prelinking just for testing purposes. Also if you'd like to run the whole system in the FIPS mode, you can disable prelink altogether on the distribution. As for the other issue that seems to be fixed by un-prelinking - I don't think this is a real conflict of libgcrypt with prelink - it rather seems that libgcrypt or prelink is somehow broken on the reporter's computer only. I am not aware of any other reports where prelinking libgcrypt made its users crashing. Thank you. |