Project

Profile

Help

Story #7984

closed

Task #7960: FIPS and support for ALLOWED_CONTENT_CHECKSUMS

As a user, Pulp will error if a disallowed hasher is attempted to be used

Added by daviddavis almost 2 years ago. Updated over 1 year ago.

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

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 90
Quarter:

Description

  1. Consolidate our calls to a new area that checks ALLOWED_CONTENT_CHECKSUMS in one place
  2. Make that available to plugin writers in the plugin API
  3. Add docs for plugin writers.
Actions #1

Updated by daviddavis almost 2 years ago

  • Description updated (diff)
Actions #2

Updated by bmbouter almost 2 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to bmbouter
  • Sprint set to Sprint 90
Actions #3

Updated by pulpbot almost 2 years ago

  • Status changed from ASSIGNED to POST

Added by bmbouter almost 2 years ago

Revision b22cf3fa

Adds a wrapper around hashlib.new()

Introducing the new, pulpcore.app.pulp_hashlib which provides the new function, a wrapper around the real hashlib.new(). This checks the ALLOWED_CONTENT_CHECKSUMS setting and raises an Exception if a hasher not declared as allowed is defined.

closes #7984

Actions #5

Updated by bmbouter almost 2 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #6

Updated by bmbouter almost 2 years ago

  • Subject changed from As a user, I can manage content with md5 checksums with FIPS enabled to As a user, Pulp will error if a disallowed hasher is attempted to be used
  • Description updated (diff)
Actions #7

Updated by ipanova@redhat.com over 1 year ago

  • Sprint/Milestone set to 3.11.0
Actions #8

Updated by ipanova@redhat.com over 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF