Project

Profile

Help

Story #8325

Task #7960: FIPS and support for ALLOWED_CONTENT_CHECKSUMS

Write a guide for changing ALLOWED_CONTENT_CHECKSUMS

Added by daviddavis 3 months ago. Updated about 1 month ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 93
Quarter:

Related issues

Blocked by Pulp - 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)CLOSED - CURRENTRELEASE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision b7268ea9 View on GitHub
Added by ppicka about 2 months ago

Allow content checksums doc

Update docs with how to properly change 'ALLOWED_CONTENT_CHECKSUMS' setting.

closes: #8325 https://pulp.plan.io/issues/8325

History

#1 Updated by daviddavis 3 months 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

#2 Updated by daviddavis 3 months 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

#3 Updated by daviddavis 3 months ago

  • Sprint/Milestone deleted (3.11.0)

#4 Updated by ppicka 2 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ppicka

#5 Updated by ppicka 2 months ago

  • Groomed changed from No to Yes
  • Sprint set to Sprint 92

#6 Updated by ppicka 2 months ago

  • Sprint changed from Sprint 92 to Sprint 93

#7 Updated by pulpbot about 2 months ago

  • Status changed from ASSIGNED to POST

#8 Updated by ppicka about 2 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#9 Updated by mdellweg about 1 month ago

  • Sprint/Milestone set to 3.12.0

#10 Updated by pulpbot about 1 month ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF