Actions
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
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 93
Quarter:
Updated by daviddavis over 3 years ago
- Tracker changed from Issue to Story
- % Done set to 0
- Severity deleted (
2. Medium) - Triaged deleted (
No)
Updated by daviddavis about 3 years ago
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).
Updated by daviddavis about 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to daviddavis
Updated by daviddavis about 3 years ago
- Sprint/Milestone set to 3.11.0
- Sprint set to Sprint 91
Updated by pulpbot about 3 years ago
- Status changed from ASSIGNED to POST
Updated by daviddavis about 3 years ago
- Sprint/Milestone changed from 3.11.0 to 3.12.0
Added by daviddavis about 3 years ago
Updated by daviddavis about 3 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|8a77316d2d73dd31d6f47b964bf148a602da6a21.
Updated by pulpbot about 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
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