-
Notifications
You must be signed in to change notification settings - Fork 236
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
<space> and ";" in folder or file names returns error #216
Comments
This is something that was likely taking place previously in v1.5, just that it was being suppressed. There has been allot of work to improve file handling in v1.6. However, these file names are certainly a mixed affair of constraints. I will do some testing this week and see what I can come up with for handling. Thanks for reporting |
@rfxn It's probably related to this - if I scan files which have spaces in filename then maldet hangs up. |
https://github.com/rfxn/linux-malware-detect/blob/master/files/internals/functions#L1181 I believe the bug is here... Try escaping the quotes:
|
fixed and committed for release in 1.6.1 |
Hi, Latest maldet version has covered the bug of escaping quotes but still getting error. Please suggest as permission is there. Jun 03 16:37:46 testbed maldet(15250): {scan} error could not read or hash /mnt/data/home/ffne9922/public_html/web/app/themes/fingo/node_modules/table/node_modules/ajv/lib/refs/$data.json, do we have permission? |
@rfxn -- Anyone able to assist ? |
Assist with what? This issue was closed in 1.6.1 |
@jhstatewide this issue, it gives permission error. |
After automatically updating to 1.6, we are seeing a lot of errors regarding file or folder names with either "" or ";"
maldet(31158): {scan} error could not read or hash ../httpdocs/tmp/templates_c/ec48cfb70f1f1843c5a24d2b3ae670db^d699142273f511bc66d93eefa94743b050a14200.module_db_tpl. navigation-tpl-009.php, do we have permission?
The error log file names look like this (chosen at random):
Let me know if you need additional information.
The text was updated successfully, but these errors were encountered: