-
Notifications
You must be signed in to change notification settings - Fork 174
docker-entrypoint.sh incorrectly sets permissions of all user uploaded files to 0755, making them executable for everybody #94
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
Comments
maybe the official redmine docs at |
Agreed, ideally the official documentation would be updated before we make any changes here. |
I've filed a bug with their issue tracker at https://www.redmine.org/issues/27538 |
I'm not sure if they are willing to update their documentation, see discussion in https://www.redmine.org/issues/27538 But as their documentation isn't tailored for the redmine-in-a-container usecase, I think you shouldn't wait for them any longer and fix the incorrect permission settings anyway. |
ok the official redmine docs have been updated: however, as in the docker container usecase most of the times files do exist when the entrypoint script gets executed, I think you should set the permissions correctly in the first place instead of removing the incorrectly set executable bit afterwards as proposed in the docs now. |
PR made: #98. Thanks @stefan-hausmann. |
just found out that after restarting my redmine container, all files uploaded by users get 0755 file permissions, which effectively makes them executable (we don't want that, do we?)
After investigating docker-entrypoint.sh (found in all current releases), I think instead of
chmod -R 755 files log tmp public/plugin_assets
you should rather use something like
instead.
The text was updated successfully, but these errors were encountered: