Bug 2213674

Summary: Workaround for hashlib.md5() without `usedforsecurity=False` in FIPS
Product: Red Hat Enterprise Linux 8 Reporter: Rayes <chhuang>
Component: python36Assignee: Python Maintainers <python-maint>
Status: CLOSED CANTFIX QA Contact: RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.7CC: cstratak, pviktori, torsava
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-12 12:16:26 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:

Description Rayes 2023-06-09 01:02:36 UTC
Description of problem:
Looking for opinion if we can add the features of hashlib.md5() from below:
https://github.com/conda/conda/pull/11658/files


Version-Release number of selected component (if applicable):
python36-3.6.8-38.module+el8.5.0+12207+5c5719bc.x86_64     
python3-libs-3.6.8-15.1.el8.x86_64


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Petr Viktorin 2023-06-12 08:10:28 UTC
I don't know if I understand "add features from https://github.com/conda/conda/pull/11658/files to python3.6 is possible" correctly. Could you clarify what features we're talking about?
Is it the usedforsecurity argument for `md5`? That is already there: RHEL's Python 3.6 allows it. (RHEL has supported it for a long time. In Python 3.9 it was added *upstream*, i.e. since 3.9 the non-RHEL distributions of Python also support it.)

At a global level, only disabling FIPS mode is possible. As said above we can't enable md5 globally and somehow leave the rest of FIPS mode on.

Comment 5 Tomas Orsava 2023-07-12 12:16:26 UTC
There hasn't been a response for a month, closing the request. Please reopen if you'd like to discuss the issue further.