-
-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restrict config write access #322
Comments
Perhaps we simply remove the attributes passing through in the default recipe (on this resource) and rely on the defaults. If you want to change to root/root you can override the config hash? |
Ah! That didn't even occur to me. I think that's a great solution. |
I may have spoke too soon. The conf.d directory is actually created by |
I think it makes sense to move that directory and set permissions accordingly. |
This fixes issue sous-chefs#322. The consul cookbook makes the Consul config writable by the same user that runs the service, which is unnecessary and could be an attack vector. This commit allows the user to specify a different set of permissions for the configuration directories (/etc/consul) than for the runtime data directory (/var/lib/consul). The config owner still defaults to 'consul' since changing it to root is a breaking change.
Hi, I am facing an issue related to config file permissions. I have overridden the default user of config and service to 'root' in wrapper cookbook :
Still, on running chef-client, it looks for consul user to add a service config :(
Can you please suggest what I am missing here to have my config files owned by root? |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The consul cookbook makes the Consul config writable by the same user that runs the service, which is unnecessary and could be an attack vector. Would you accept a pull request which adds a couple new attributes and uses them for the ownership of
/etc/consul
?The text was updated successfully, but these errors were encountered: