Bug 1430811 - [RFE] Do not use NOPASSWD in /etc/sudoers.d/foreman-proxy
Summary: [RFE] Do not use NOPASSWD in /etc/sudoers.d/foreman-proxy
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Puppet
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-09 15:58 UTC by Barbora Vassova
Modified: 2020-08-13 08:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-16 13:51:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Barbora 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: 
-

Comment 1 Marek Hulan 2017-03-09 16:06:31 UTC
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.

Comment 2 Barbora Vassova 2017-03-16 13:51:32 UTC
Hello, 
customer that requested this feature enhancement decided that they do not require it anymore.


Note You need to log in before you can comment on or make changes to this bug.