Project

Profile

Help

Issue #4190

closed

Tag names starting with `sha256:` could cause collisions

Added by amacdona@redhat.com almost 4 years ago. Updated 10 months ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

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.

Actions #1

Updated by CodeHeeler almost 4 years ago

  • Triaged changed from No to Yes
Actions #2

Updated by ipanova@redhat.com over 3 years ago

  • Tags Pulp 3 added
Actions #3

Updated by bmbouter over 3 years ago

  • Tags deleted (Pulp 3)
Actions #4

Updated by ipanova@redhat.com almost 3 years ago

  • Project changed from Docker Support to Container Support
Actions #5

Updated by ipanova@redhat.com 10 months ago

  • Status changed from NEW to CLOSED - WONTFIX

Also available in: Atom PDF