Story #8325: Write a guide for changing ALLOWED_CONTENT_CHECKSUMS - Pulp

Actions

Send by e-mail Copy link

Story #8325

closed

Task #7960: FIPS and support for ALLOWED_CONTENT_CHECKSUMS

Write a guide for changing ALLOWED_CONTENT_CHECKSUMS

Added by daviddavis about 3 years ago. Updated about 3 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

ppicka

Category:

Sprint/Milestone:

3.12.0

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Yes

Sprint Candidate:

Tags:

Sprint:

Sprint 93

Quarter:

Related issues

Actions

Copy link

Updated by daviddavis about 3 years ago

Rough PoC:

Pulp can prohibit or allow checksums by setting the ALLOWED_CONTENT_CHECKSUMS setting. Changing this setting requires a few steps.

First, before you change the setting, see how your Pulp instance will be impacted by this change by running:

<insert task info from https://pulp.plan.io/issues/7986>

Before switching, any on-demand repos containing forbidden checksum digests will need to be synced with policy immediate to populate missing allowed checksums. Alternatively, users can remove these offending repo versions followed by orphan cleanup.

If you have artifacts that do not conform to your ALLOWED_CONTENT_CHECKSUMS setting, you can update them using:

pulpcore-manager handle-artifact-checksums

Actions

Copy link

Updated by daviddavis about 3 years ago

Blocked by Story #7986: As a user, I can evaluate a “what-if scenario” by generating a report of impacted content from a set of user provided checksums (not from ALLOWED_CONTENT_CHECKSUMS) added

Actions

Copy link