-
Notifications
You must be signed in to change notification settings - Fork 102
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
Minimize access needs a better way of removing +w on system folders #60
Comments
spielkind
added a commit
to TelekomCloud/puppet-os-hardening
that referenced
this issue
Jun 24, 2015
This commit fixes dev-sec#60
|
Wouldn't call it a fix, but maybe a workaround or interim solution (at least for the first case). |
rooprob
added a commit
to rooprob/puppet-os-hardening
that referenced
this issue
Aug 27, 2015
Issue: dev-sec#60 From this page ubuntu linking ```/usr/bin/X11 -> .``` is by design: http://askubuntu.com/questions/191654/why-are-there-infinitely-many-x11-subdirectories-in-usr-bin-x11 This modification says ```links => follow``` is inappropriate. The specification of directories to apply this file resource is good, so it should cover the desired scope: that any files contained herein should be set as per the resource. Any files outside, including symlink targets should be untouched. Any files which are symlinked to other files inside will be caught, and any symlinks, self-referential or otherwise, will be ignored. This would resolve issue 60.
|
Should be fixed now by #116 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I came across two different issues with symlinks (that already existed on VM images I was deploying)
/usr/bin/X11targeting itselfX11 -> .causing the following error:I agree that the image itself should have this things fixed, but it might be worth considering a better approach that would deal with this type of issues in this module.
The text was updated successfully, but these errors were encountered: