Bug 691449 (BaseOS-FIPS-Tracker)

Summary: [RHEL6] FIPS-140-2 Problem Tracker
Product: Red Hat Enterprise Linux 6 Reporter: Eduard Benes <ebenes>
Component: distributionAssignee: Eduard Benes <ebenes>
Status: CLOSED WONTFIX QA Contact: Eduard Benes <ebenes>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.1CC: casmith, jjaburek, ohudlick, omoris, pwouters, rstclair, sgrubb
Target Milestone: rcKeywords: Tracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-30 08:31:42 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:
Bug Depends On: 574770, 612053, 618595, 674747, 689387, 691394, 697938, 705097, 717709, 736423, 783158, 802364, 805676, 817066, 817067, 836178, 854384, 871775, 883460, 956360, 962648, 983292, 1088778, 1148032, 1174775    
Bug Blocks:    

Description Eduard Benes 2011-03-28 15:09:44 UTC 
This is a tracking bug for general FIPS related issues which do not directly affect the certification.

Issues affecting the certification (openssl, openssh, libgcrypt, openswan, kernel) are tracked in bug 661821.
Comment 2 RHEL Program Management 2011-03-28 15:38:15 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 3 Robert St Clair 2012-03-20 17:01:44 UTC 
Was working with a customer that has several RHEL5.8 servers fully updated and said that when his systems are in FIPs 14-2 mode, Squid also does not work.
Comment 4 Robert St Clair 2012-03-20 17:02:45 UTC 
Was working with a customer that has several RHEL5.8 servers fully updated and
said that when his systems are in FIPs 140-2 mode, Squid also does not work.
Comment 5 Paul Wouters 2012-06-18 14:31:10 UTC 
I wrote a patch for squid, see https://bugzilla.redhat.com/show_bug.cgi?id=705097