Skip to content
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

decide how to deal with sudo/administrative issues #23

Open
kristovatlas opened this issue May 2, 2016 · 2 comments
Open

decide how to deal with sudo/administrative issues #23

kristovatlas opened this issue May 2, 2016 · 2 comments

Comments

@kristovatlas
Copy link
Owner

It's probably a good practice to mostly use a non-admin account, but the non-admin won't be able to change configurations unless at least added to the sudoers list. Need to decide how to resolve this catch-22.

@kristovatlas
Copy link
Owner Author

@kristovatlas
Copy link
Owner Author

#4 partially resolved this by always trying to perform checks and implement fixes without sudoers rights. I think the next step is just to clarify the README to state that the script should be executed once per user. I may also want to output some direction to the user in the case that a config fix is user-specific && the fix requires admin rights && the user doesn't have admin rights; if there are any configs that match this pattern, I must weigh the risk of adding the user to the sudoers file vs. not having the desired configuration, or examine other options for escalating privileges other than sudo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant