Task #7960: FIPS and support for ALLOWED_CONTENT_CHECKSUMS
As an installer user, I don't have special FIPS detection
The installer's FIPS features are described here. This is problematic in a few ways.
- Pulp is on the hook to rebase the django-forked-and-patched everytime upstream Django puts out a CVE release. This puts Pulp on the critical path for CVE releases, which is not a good arrangement.
- Users are using bits in production that aren't available on PyPI. This is unusual
- The installer adjusts the value for
ALLOWED_CONTENT_CHECKSUMSinstead of letting pulpcore's default prevail. With 3.11 md5 and sha-1 are being removed, so the installer should no longer adjust this.
- Remove the FIPS docs page.
- Remove the installer codepaths related to FIPS
- No longer install the branched checkout https://github.com/mdellweg/django/tree/fips and instead receive Django from PyPI as usual.
- Provide some documented instructions for dev environments on the django and pulpcore patches they need to apply for dev environments (since the installer will no longer do this). (Consider putting into pulp_devel role, or depending on vars like pulp_source_dir.)
I think we could run these commands in the dev and test environments to patch django:
django_location=$(pip show django | grep Location | cut -d' ' -f2) sed -i 's/hashlib.md5()/hashlib.md5(usedforsecurity=False)/' "$django_location/django/db/backends/utils.py"
For a dev and test environment, I'm +1 to this.
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset ansible-pulp|ae47f49ef9b79cd79851d0caa245559ceabbc7ce.
Please register to edit this issue