Project

Profile

Help

Story #2625

As a user, I can sync content trusted manifests

Added by ipanova@redhat.com 6 months ago. Updated 5 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
% Done:

0%

Platform Release:
Blocks Release:
Target Release - Docker:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No

Description

During sync we fetch manifests from registry by tag. Yes we do some digest verification but it is not enough. What we do is that we compare docker-content-digest received in the response headers with calculated digest from fetched json.

To properly verify it, we need to know what digest to expect. It doesn't add any security to check against the Docker-Content-Digest returned by the registry, since if the manifest is replaced with a malicious one, the Docker-Content-Digest will also change to match that malicious manifest.

I still do not have enough information how we could solve all this, but the current approach definitely does not protect us from malicious intents

History

#1 Updated by ipanova@redhat.com 6 months ago

  • Description updated (diff)

#2 Updated by ipanova@redhat.com 6 months ago

  • Description updated (diff)

#3 Updated by ipanova@redhat.com 5 months ago

  • Tracker changed from Issue to Story
  • Subject changed from Syncronyzed manifests are not content trusted to As a user, I can sync content trusted manifests
  • % Done set to 0

Please register to edit this issue

Also available in: Atom PDF