Story #7989
closed
Task #7960: FIPS and support for ALLOWED_CONTENT_CHECKSUMS
As a client, I get an error message when I try to consume on_demand content with a checksum that is not in ALLOWED_CONTENT_CHECKSUMS
Status:
CLOSED - CURRENTRELEASE
- Tracker changed from Issue to Story
- % Done set to 0
- Severity deleted (
2. Medium)
- Triaged deleted (
No)
One edge case here that I think we need to handle: when a client requests a content artifact that has 2 RemoteArtifacts (one without any allowed checksums), the content app needs to be smart and pick the one that has the allowed checksum(s).
- Status changed from NEW to ASSIGNED
- Assignee set to daviddavis
- Sprint/Milestone set to 3.11.0
- Sprint set to Sprint 91
- Status changed from ASSIGNED to POST
- Sprint/Milestone changed from 3.11.0 to 3.12.0
- Sprint changed from Sprint 91 to Sprint 92
- Sprint changed from Sprint 92 to Sprint 93
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
Have the content app handle UnsupportedDigestValidationError
In https://pulp.plan.io/issues/8435 we added a check to downloader to prevent the download of files without allowed checksums. This code updates the downloader to handle the exception that gets raised.
fixes #7989