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:
If you sync a container image in Satellite, it is published to a URL that can be accessed from any machine with connectivity to Satellite. Even if the content view to which the machine is subscribed provides access to no Docker content, you can pull any container. Although Satellite provides the ability to manage images through content views, there's no need to actually do so - you can simply access any container sync'd to Satellite.
Version-Release number of selected component (if applicable):
Satellite 6.2.5
How reproducible:
Every time
Steps to Reproduce:
1. Sync a container to Satellite
2. Use the URL provided by Satellite to do a docker pull on any machine, regardless of whether or not that machine should have access to the content
3.
Actual results:
Container successfully pulls. This could provide access to software not intended to run on a particular machine, access to data (or whatever else) in the container, etc.
Expected results:
This should function like all other Satellite content.
If the content has not been promoted to the environment in which the machine is subscribed, no access should be allowed.
Additional info:
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.