Bug 833086

Summary: squid uses a private md5 hash function for user auth, bypassing FIPS 140-2 restrictions
Product: Red Hat Enterprise Linux 6 Reporter: Paul Wouters <pwouters>
Component: squidAssignee: Michal Luscon <mluscon>
Status: CLOSED ERRATA QA Contact: Dalibor Pospíšil <dapospis>
Severity: high Docs Contact:
Priority: high    
Version: 6.5CC: omoris, ovasik, prc
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: squid-3.1.10-14.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 833216 1322364 (view as bug list) Environment:
Last Closed: 2013-02-21 08:39:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 717789, 833216    
Attachments:
Description Flags
md5 fips and crypt patch none

Description Paul Wouters 2012-06-18 14:40:09 UTC
Description of problem:
For details, see #705097

Comment 2 Paul Wouters 2012-06-18 21:15:29 UTC
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.

Comment 3 RHEL Program Management 2012-07-10 08:18:06 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 4 RHEL Program Management 2012-07-11 02:02:40 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 12 errata-xmlrpc 2013-02-21 08:39:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0505.html