-
Notifications
You must be signed in to change notification settings - Fork 15
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
permissions: worldWritable not working for unprivileged users #44
Comments
In my experience with typical Linux/OSX/Solaris systems, it should be acceptable for an unprivileged Unix user to run If that's not working, then probably something else in the build process is running as a different user. (Example: maybe someone ran I think it's better policy to avoid Suggestions:
|
Thanks, I understand your point and must have botched something in the process. Rather than worldWritable I am trying to implement a policy that uses the owner set to the current user and the group set to apache. This way I can remove the 'other' permissions and have something slightly more secure. Will report when completed. |
Ah, nice idea. If you can get it to work, then it could be more reliable than 'worldWriteable' and more portable than |
That's what I thought. I'll give it a try and report back - probably ------ Original Message ------
|
In file: app/defaults/services.yml, shouldn't we have:
Otherwise amp is only usable if you are root.
The text was updated successfully, but these errors were encountered: