Project

Profile

Help

Actions
Send by e-mail Copy link

Task #8342

closed

Task #7960: FIPS and support for ALLOWED_CONTENT_CHECKSUMS

Document that the ALLOWED_CONTENT_CHECKSUMS is not fully enforcing everywhere

Added by bmbouter almost 4 years ago. Updated almost 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
bmbouter
Category:
-
Sprint/Milestone:
3.11.0
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.

Actions
Copy link
 #1

Updated by bmbouter almost 4 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to bmbouter
Actions
Copy link
 #2

Updated by pulpbot almost 4 years ago

  • Status changed from ASSIGNED to POST

Added by bmbouter almost 4 years ago

Revision 8d1a2b4e | View on GitHub

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

Actions
Copy link
 #3

Updated by bmbouter almost 4 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by ipanova@redhat.com almost 4 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Send by e-mail Copy link

Also available in: Atom PDF