Bug 1312859

Summary: [RFE] Backport FIPS mode workaround for hashlib from RHEL-6
Product: [Fedora] Fedora EPEL Reporter: Hubert Kario <hkario>
Component: python26Assignee: Adrien Devresse <adev88>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el5CC: adev88, derks, dmalcolm, jeffrey.ness
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-06 10:03:41 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:

Description Hubert Kario 2016-02-29 12:06:24 UTC 
Description of problem:
When hashlib is used for calculating MD5 digest and the system is running in FIPS mode, the OpenSSL implementation will abort process

Version-Release number of selected component (if applicable):
python26-2.6.8-2.el5.x86_64

How reproducible:
always

Steps to Reproduce:
1. Enable FIPS mode in RHEL-5
2. use hashlib module to calculate MD5 hash
3.

Actual results:
digest.c(151): OpenSSL internal error, assertion failed: Digest update previous FIPS forbidden algorithm error ignored

Expected results:
ValueError raised, usedforsecurity parameter to new() supported

Additional info:
The feature is implemented in python-2.6.5-hashlib-fips.patch in RHEL-6 package
Comment 1 Fedora End Of Life 2017-04-06 10:03:41 UTC 
Fedora EPEL 5 changed to end-of-life (EOL) status on 2017-03-31. Fedora EPEL 5
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
or Fedora EPEL, 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.