Project

Profile

Help

Actions
Send by e-mail Copy link

Story #9510

closed

Story #9502: [EPIC] Contrainer Signing and Verification

As a user I can host container image signatures

Added by ipanova@redhat.com over 3 years ago. Updated about 3 years ago.

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

0%

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

Description

Ticket moved to GitHub: "pulp/pulp_container/501":https://github.com/pulp/pulp_container/issues/501

Signatures that were:

  • mirrored from remote source
  • produced by Pulp Container Registry
  • pushed into Pulp Container Registry by clients

will be available at the signature extensions API.

Add new Signature model which will have many to one relationship to the Manifest. On manifest deletion, it's signatures will be also removed.

Q: store the signature in the DB ( it is a json file) or as an artifact? In DB

Q: store the signature as manifests part of docker v2 api ( make it cosign like, but skopeo/podman do not support that yet) we will not support this for now

Actions
Copy link
 #1

Updated by ipanova@redhat.com over 3 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by ipanova@redhat.com over 3 years ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by ipanova@redhat.com over 3 years ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by ipanova@redhat.com over 3 years ago

  • Description updated (diff)
Actions
Copy link
 #5

Updated by ipanova@redhat.com over 3 years ago

  • Description updated (diff)
Actions
Copy link
 #6

Updated by ipanova@redhat.com over 3 years ago

  • Description updated (diff)
Actions
Copy link
 #7

Updated by pulpbot about 3 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE
Actions
Send by e-mail Copy link

Also available in: Atom PDF