Bug 516549 - Does libgcrypt need to be blacklisted from prelink?
Summary: Does libgcrypt need to be blacklisted from prelink?
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: libgcrypt
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-10 12:07 UTC by Tim Waugh
Modified: 2009-08-10 13:09 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-08-10 12:31:37 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Tim Waugh 2009-08-10 12:07:31 UTC 
In bug #506796 there is some discussion of prelink causing problems with libgcrypt.  Is this the case?  Should it be blacklisted?
Comment 1 Tomas Mraz 2009-08-10 12:31:37 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.
Comment 2 Tim Waugh 2009-08-10 13:09:15 UTC 
Thank you.
Note You need to log in before you can comment on or make changes to this bug.