+++ This bug was initially created as a clone of Bug #833086 +++ Description of problem: For details, see #705097 --- Additional comment from pwouters on 2012-06-18 17:15:29 EDT --- Created attachment 592755 [details] md5 fips and crypt patch Patch to only allow private md5 functions for local disk file hash identifiers, but not for user authentication or network access to ensure compliance with fips.This also addresses an issue with crypt() possible returning NULL.
Created attachment 592770 [details] fips/crypt patch for fedora version Attached is the fedora version of the same patch
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.
Lubos, please discuss this change with the upstream. Thank you!
Just to make sure... Paul, did you report this to the upstream? If yes, would you mind attaching a link to the discussion or upstream bug? Thank you in advance.
See email thread: http://www.squid-cache.org/mail-archive/squid-dev/201206/0074.html
(In reply to Paul Wouters from comment #8) > See email thread: > http://www.squid-cache.org/mail-archive/squid-dev/201206/0074.html Hi Paul, I read that email thread, and it seems like, upstream is not going to use your patch. If you would like to have this patch in Fedora, please try to discuss it with upstream and try to convince them to use your patch, but we are not going to use your Patch as downstream. So I'm closing this bug as UPSTREAM.
ok, that means squid will crash when fedora runs in FIPS mode. I think that's not the best outcome here. And it will make live harder for whoever has the pleasure of maintaining squid in RHEL, as they will surely get hit by this (there have been rhbz's in the past for this)
(In reply to Paul Wouters from comment #10) > ok, that means squid will crash when fedora runs in FIPS mode. > > I think that's not the best outcome here. And it will make live harder for > whoever has the pleasure of maintaining squid in RHEL, as they will surely > get hit by this (there have been rhbz's in the past for this) OK, let's leave the bug open for tracking purposes. Although since you seem to be the person pursuing this change, it would be for the best if you could convince the upstream to include the patch.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.