-
Notifications
You must be signed in to change notification settings - Fork 492
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
mina/foreman does not work due to sudo #233
Comments
If it is possible for you on your system (some production systems will not allow this), add
|
@mcescalante adding |
Right, it being a security risk is what my intentions were by including the "possible on your system" part. If one was deploying to an isolated test environment and didn't want to keep adding & removing command whitelist lines to sudoers, adding that as a temporary solution until ready to a production deploy may be okay. I agree this should absolutely not be used in production. As you mentioned, whitelisting the specific commands necessary is the most secure & elegant solution. Clearly, my answer was poor - thanks for posting in here to clarify especially if future users are trying to address something like this 😄 |
Ok, we have a nice solution, so I can close this "issue". |
@gabskoro could you include my example |
Every sudo command fails to run:
The text was updated successfully, but these errors were encountered: