Actions
Task #8342
closedTask #7960: FIPS and support for ALLOWED_CONTENT_CHECKSUMS
Document that the ALLOWED_CONTENT_CHECKSUMS is not fully enforcing everywhere
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
In the settings area that documents the ALLOWED_CONTENT_CHECKSUMS we need to clarify with 3.11 that pulpcore or plugins may make calls to checksums that are disallowed.
Solution¶
Add a banner onto the setting itself that identifies this risk.
Updated by bmbouter almost 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
Updated by pulpbot almost 4 years ago
- Status changed from ASSIGNED to POST
Added by bmbouter almost 4 years ago
Updated by bmbouter almost 4 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|8d1a2b4e9c0b2641ad2690051127dbf957151bf5.
Updated by ipanova@redhat.com over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Document ALLOWED_CONTENT_CHECKSUMS as not finished
The ALLOWED_CONTENT_CHECKSUMS is not fully enforcing with 3.11, so this adds a banner to the settings page that identifies this for users.
closes #8342