You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had to adjust a few things to make the malware detection work.
I had the following problems:
manual scanning was not possible
scanning of files/folders with the user/group permission root:root was not possible
the directory /shareboxx/files was not scanned
To be able to scan manually, I had to change the value of scan_user_access from 0 to 1 in the file /usr/local/maldetect/conf.maldet.
To be able to scan files/folders with root:root permissions I had to change the value of scan_ignore_root from 1 to 0 in the file /usr/local/maldetect/conf.maldet.
After installing the clamav-testfiles package, I was then able to scan the testfiles manually:
sudo maldet -a /usr/share/clamav-testfiles
sudo maldet --report
Regarding the last problem, I had to edit the service.
I had to adjust a few things to make the malware detection work.
I had the following problems:
To be able to scan manually, I had to change the value of
scan_user_access
from0
to1
in the file/usr/local/maldetect/conf.maldet
.To be able to scan files/folders with root:root permissions I had to change the value of
scan_ignore_root
from1
to0
in the file/usr/local/maldetect/conf.maldet
.After installing the clamav-testfiles package, I was then able to scan the testfiles manually:
Regarding the last problem, I had to edit the service.
This is what it looked like before editing:
It is about the line that starts with
ExecStart
.According to this output, the folders
/dev/shm
,/var/tmp
and/tmp
were monitored:I customized the line that starts with
ExecStart
(withsudo nano /usr/local/maldetect/conf.maldet
):The
/shareboxx/files
folder is now monitored:Before the adjustment, uploaded testfiles were not recognized, but after the adjustment they were.
And don't forget to restart everything after the changes:
Further reading:
The text was updated successfully, but these errors were encountered: