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

Permissions not set correctly #1453 #1454

Merged
merged 1 commit into from
Jul 17, 2015
Merged

Permissions not set correctly #1453 #1454

merged 1 commit into from
Jul 17, 2015

Conversation

markshust
Copy link
Contributor

No description provided.

@vancoz vancoz added the PS label Jul 10, 2015
@fooman
Copy link
Contributor

fooman commented Jul 12, 2015

You are currently only changing to 644 which still allows anyone with system access to read the files. I think there will always be a need for the person deploying to accurately set permissions for their system requirements but if permissions are changed I would advocate to change the default to the strictest possible (700/600). This would then make giving extra permissions an explicit step.

@markshust
Copy link
Contributor Author

@fooman git only tracks perms of 644/755 i believe. this ticket was just to tighten up the files that were set to 755 (all files should be 644 except bin/magento).

@magento-team magento-team merged commit a9f97fc into magento:develop Jul 17, 2015
@markshust markshust deleted the master branch July 20, 2015 14:24
magento-team pushed a commit that referenced this pull request Sep 4, 2017
Fixed issues:
- MAGETWO-72261: Merge 2.2-develop into develop
magento-engcom-team added a commit that referenced this pull request Mar 16, 2018
 - Merge Pull Request magento-engcom/magento2ce#1454 from magento-engcom/magento2ce:codetriage-badge-2.1
 - Merged commits:
   1. a745fc5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants