Project

Profile

Help

Issue #4190

Tag names starting with `sha256:` could cause collisions

Added by amacdona@redhat.com 12 months ago. Updated about 20 hours ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Severity:
2. Medium
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

This is a weird edge case to be sure. Here are the urlpatterns:

url(r'^v2/(?P<path>.+)/manifests/(?P<digest>sha256:[A-Fa-f0-9]+)$',
url(r'^v2/(?P<path>.+)/manifests/(?P<tag_name>[A-Za-z0-9\._-]+)$',

So if a tag is allowed to conform with `sha256:[A-Fa-f0-9]+)$`, it will resolve to the tag view instead of the BlobManifest view.

History

#1 Updated by CodeHeeler 12 months ago

  • Triaged changed from No to Yes

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

  • Tags Pulp 3 added

#3 Updated by bmbouter 7 months ago

  • Tags deleted (Pulp 3)

#4 Updated by ipanova@redhat.com about 20 hours ago

  • Project changed from Docker Support to Container Support

Please register to edit this issue

Also available in: Atom PDF