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

trunk: mitigate restrictive umask #1294

Closed
robocoder opened this issue Apr 7, 2010 · 6 comments
Closed

trunk: mitigate restrictive umask #1294

robocoder opened this issue Apr 7, 2010 · 6 comments
Assignees
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@robocoder
Copy link
Contributor

Technically, an overly restrictive umask is a web server misconfiguration.

If the umask is too restrictive, e.g., 0222, then files created by tempnam() are read-only. This is problematic for libs/Smarty/internal/core.write_file.php, core/CacheFile.php, libs/Zend/Http/Client.php.

A workaround would be to: @chmod($file, 0600) after calling tempnam().

@robocoder
Copy link
Contributor Author

A related issue is when we mkdir/copy with 0755.

@robocoder
Copy link
Contributor Author

(In [3772]) refs #1294 - mkdir wrapper inconsistencies

@robocoder
Copy link
Contributor Author

(In [3773]) refs #1294 - chmod() after tempnam() to undo a restrictive umask

@robocoder
Copy link
Contributor Author

(In [3774]) refs #1294 - chmod() after mkdir() to mitigate restrictive umask

@mattab
Copy link
Member

mattab commented May 25, 2011

Is there still work to do or fixed or wontfix?

@robocoder
Copy link
Contributor Author

nothing else planned for this ticket

@robocoder robocoder added this to the 1.5 - Piwik 1.5 milestone Jul 8, 2014
@robocoder robocoder self-assigned this Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

No branches or pull requests

2 participants