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
Plugin file permissions #528
Comments
I'm always a bit hesitant to "fix" issues which haven't been seen in a decade... in particular when they scream "platform support!", too 😀. Would you have a one line fix for this ready to be tested? |
mavit
added a commit
to mavit/slimserver
that referenced
this issue
Feb 7, 2021
On Unix-like platforms, ensure that plugins are installed in such a way that none of their files are writable by users other than the user running LMS, even if theyʼre stored that way in the plugin ZIP file. Fixes LMS-Community#528.
I'm afraid it stretches to five lines, including a comment. See e36c865. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For my LMS plugin, I'm using GitLab to automatically pack the latest Git commit into a downloadable zip. It turns out that the default GitLab umask was 0000, and this was carrying over to the permissions of files inside my zip. When LMS downloads and installs the plugin, it respects these permissions, with the outcome that the files for my plugin were all
a=rw
.This doesn't seem like something that anyone would ever want. Would it be a sensible precaution to reset the permissions to, say,
u=rw,go=r
when unpacking?The text was updated successfully, but these errors were encountered: