-
Notifications
You must be signed in to change notification settings - Fork 166
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
fix: permissions on sudoers include dir were wrong #70
Conversation
This PR should be merge as soon as possible as it could lock people out of server |
Thanks for providing this fix @kmosher (and appreciate the confirmation, @jynolen). One question, is @daks Regression introduced in #66. Perhaps we should merge this ASAP and then finalise whether it should be |
Agreed first fix, after find a better solutions. |
This is what i got when the folder perm is 440
According to search that includes
-- Restoring default package perms
-- Trying again with debian user
More over here the content of sudoers.d README
|
Not sure why I set it to One improvement could be to add a basic test on this directory mode, here https://github.com/saltstack-formulas/sudoers-formula/blob/master/test/integration/default/controls/config.rb, with something like
A better one (but I'm not sure I know how to run it) would be to set some |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK for me, see previous comment for optional test.
I will merge this PR as it is, we can add the inspec test later |
Added #71 as a reminder for what still could/should be done. |
🎉 This PR is included in version 0.23.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]
Changes related to the build system[chore]
Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]
Changes to the continuous integration configuration[feat]
A new feature[fix]
A bug fix[perf]
A code change that improves performance[refactor]
A code change that neither fixes a bug nor adds a feature[revert]
A change used to revert a previous commit[style]
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]
Documentation changes[test]
Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE
?No.
Related issues and/or pull requests
Describe the changes you're proposing
sudo started throwing errors about not being able to stat files in
/etc/sudoers.d
after pulling the latest version. Tracked it down to a missing +x permission on the include directory that was brought under salt management in the prior commit.Pillar / config required to test the proposed changes
N/A
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context