Issue #3345. Synchronize umask for cp_dav service and permissions that we are granting during file and folder creation on API #3346
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SilinPavel
force-pushed
the
issue_3345_sync_umask_for_webdav_and_api_storage_operations
branch
from
b4f0abe
to
d53237d
Compare
…t we are granting during file and folder creation on API
SilinPavel
force-pushed
the
issue_3345_sync_umask_for_webdav_and_api_storage_operations
branch
from
d53237d
to
2e904f9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #3345
CP_FILE_SHARE_STORAGE_DEFAULT_UMASKenv to use it incp-davandcp-api-srvTaking in consideration that in Linux the default maks for files is
666and folders777, logic in thecp-api-srvas follow:umaskfromCP_FILE_SHARE_STORAGE_DEFAULT_UMASK