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.
DescriptionBarbora Vassova
2017-03-09 15:58:44 UTC
Business Case:
/etc/sudoers.d/foreman-proxy prevents the need for re-authentication, based on the following lines:
foreman-proxy ALL = (root) NOPASSWD : /usr/bin/puppet cert *
foreman-proxy ALL = (root) NOPASSWD : /usr/bin/puppet kick *
Customer (and their security audit software) considers this a security risk, since these lines cannot be commented out. They would like this to be changed so that NOPASSWD isn't used.
Technical Requirements:
-
Additional information:
-
How would the customer want to trigger the puppet under privileged account (root) if the capsule runs under non-privileged (user) account? I can't think of safer way atm. Running capsule under root (one could probably configure it this way already) seems like a less secure way. It would be a different story if they didn't use puppet cert and kick features, in such case they could comment this and be careful on upgrades since the installer would try to override the file.