Motivation.
After installing and running the security_review module 8.x-1.x I found the language for the details of the File system permissions to be a bit confusing.
I propose language like this:
In addition to inspecting existing directories,
this test attempts to create and write to your file system. Look in
your security_review module directory on the server for:
-
A file named: file_write_test.YYYYMMDDHHMMSS
-
If this file exists the web server can write files to the
security_review module directory and perhaps to other directories.
You should correct the file permissions on all code directories of
your Drupal installation.
-
If this file exists the web server can write files to the
-
Open the file IGNOREME.txt.
-
If a timestamp is appended at the end of
it. That means the web server has permission to write to your files.
This is insecure and the permissions should be corrected.
-
If a timestamp is appended at the end of
The intent is to make it clear to the user what the tests are doing and what they should check for to see if there file permissions are secure. For example it was not clear to me that the test on the IGNOREME.txt was trying to write to the contents of that file as opposed to renaming it.
patch forthcoming.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | 2535944-12.patch | 3.13 KB | sandeepsingh199 |
| #6 | security_review-add-translation-2535944-6-drupal8.patch | 3.14 KB | serundeputy |
| #5 | security_review-add-translation-2535944-5-drupal8.patch | 209.03 KB | serundeputy |
| #2 | security-review-file-permissions-test-2535944-2.patch | 2.44 KB | serundeputy |
Issue fork security_review-2535944
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #1
serundeputy commentedComment #2
serundeputy commentedHere is a patch with the proposed language.
Comment #3
serundeputy commentedComment #4
c-logemannI didn't made a review of your text. But I see in your patch that you add some text without t()-function. Especially security information should be translated in my opinion.
Comment #5
serundeputy commented@C_Logemann thanks for your review!
I've added `t()` to the markup in this patch.
~Geoff
Comment #6
serundeputy commentedsorry last patch was no good; re-roll.
Comment #7
vuilI close the issue as Closed (outdated) for non-activity since 19 Jul 2015, it can not be apply and it's totally outdated.
Comment #8
c-logemannClosing an issue because nobody helps doesn't make it "oudated". This issue is about current Drupal 8 Dev version and just need a review help.
Especially file system checks are very important. So I think a feature request about explaining users what's going on in this security area is also very important.
Comment #9
vuilOK, I agree @c_logemann. But then set the issue to Needs work because the patch can not be applied on the current 8.x-1.x-dev branch, it needs to be updated and/or re-rolled. Thank you!
Comment #10
c-logemannWhen the patch can't apply anymore "needs work" is correct. I try to find some time going forward with this feature and other file check improvements.
Comment #11
smustgrave commentedComment #12
sandeepsingh199 commentedhello team, I have re-rolled the #6 patch for current 8.x-1.x-dev branch with D9.5.x. kindly check & review. Thanks.
Comment #13
smustgrave commentedComment #14
smustgrave commentedTests are now passing thank you!
Comment #17
smustgrave commentedComment #18
c-logemannWhen I read the (new) description of this test I think there is lots of space for file checking improvement. But when the test currently is working in this way the text should reflect this. When I find some time I will open a new issue.
Thanks @smustgrave for cleaning up some issues of this module.
Comment #19
tobiasbfyi: Potx will skip the new string, because it finds/use only plain strings. (l.d.o.)
So the t can be removed or the string needs to wrapped with t.