Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: The Pulp streamer uses a base64 encoded "time-bombed" URL to serve content. If the base64 encoding ends up padding the key with more than one '=' sign, Pulp will 403 the request and raise a stack trace.
Its difficult to reproduce a signature with extra '=' signs without resorting to curl commands, but the curl command can reliably do it.
How reproducible: every time
Steps to Reproduce:
1. see https://pulp.plan.io/issues/2031#note-5
Actual results: If you curl a known working URL with a bad signature with extra ='s (you can copy/paste the one from the pulp issue), you'll get a 403 with stack trace
Expected results: the example curl command in the pulp issue should 403 without stack trace. In a "real" scenario with a correct signature, it would 200.
Additional info:
https://en.wikipedia.org/wiki/Base64#Padding has info on when a URL will be padded with extra ='s.
Comment 3pulp-infra@redhat.com
2016-06-24 18:00:21 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 4pulp-infra@redhat.com
2016-06-24 18:00:24 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 5pulp-infra@redhat.com
2016-07-05 14:00:30 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 6pulp-infra@redhat.com
2016-07-12 20:30:59 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 7pulp-infra@redhat.com
2016-07-18 19:30:44 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:2108