Skip to content
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

Why are the permissions for blobs hardcoded to give only the user access? #155

Closed
enfold-josh opened this issue Apr 7, 2017 · 2 comments · Fixed by #156
Closed

Why are the permissions for blobs hardcoded to give only the user access? #155

enfold-josh opened this issue Apr 7, 2017 · 2 comments · Fixed by #156
Labels

Comments

@enfold-josh
Copy link

Currently the blobs code creates directories with permissions giving only user read, write and execute and files with permissions giving only user read. This is hardcoded and impossible to change without patching.

We have a client that wants to use solr to index content. To index blobs using collective.solr solr requires permissions to access the blobs on the filesystem. Currently without patching this would require the solr process to run as the same user as the zope processes. This is problematic because the solr process would then have write access to the blobstorage directories.

@jimfulton
Copy link
Member

This is a horrible misfeature.

@jimfulton
Copy link
Member

Note: #1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants