Maldet ignore files in /var/www/vhosts about linux-malware-detect HOT 5 CLOSED

Hello,

I sometimes had the same issue when I was running a manual scan on CentOS 6. For example, let's say that my current path in the shell is /home/user1/ . If I would put in the command maldet -a public_html/, it would give me the same error as you provided. But if I changed the current path to, let's say "/" (cd / ), and then try to scan the same user, but with the absolute path, it would work:

maldet -a /home/user1/public_html/

Please let me know if it worked for you. Also, you should try Maldet 1.5 to see if the problem is solved. I didn't encounter this issue anymore since I installed the 1.5 version.

Thank you.

from linux-malware-detect.

Hello,

With the absolute path doesn't work but with I installed now the 1.5
version nd it work. Thank you.

Regards

2015-08-20 8:28 GMT+02:00 AndreiHavri [email protected]:

Hello,

I sometimes had the same issue when I was running a manual scan on CentOS
6. For example, let's say that my current path in the shell is /home/user1/
. If I would put in the command maldet -a public_html/, it would give me
the same error as you provided. But if I changed the current path to, let's
say "/" (cd / ), and then try to scan the same user, but with the absolute
path, it would work:

maldet -a /home/user1/public_html/

Please let me know if it worked for you. Also, you should try Maldet 1.5
to see if the problem is solved. I didn't encounter this issue anymore
since I installed the 1.5 version.

Thank you.

—
Reply to this email directly or view it on GitHub
#56 (comment)
.

from linux-malware-detect.

Hello,

Glad to hear that 1.5 works for you. Just to be more clear, the above workaround wasn't about giving the absolute path to the maldet -a command, but to change the current working directory from which you give the command.

For example, if you're in /home/ and you enter maldet -a /home/user3/public_html and you get the error you specified, simply try to change the directory you are in (let's say / or /usr ) and try again the command maldet -a /home/user3/public_html/

Regards.

from linux-malware-detect.

Ach so. Ok. Thank you.

2015-08-23 21:51 GMT+02:00 AndreiHavri [email protected]:

Hello,

Glad to hear that 1.5 works for you. Just to be more clear, the above
workaround wasn't about giving the absolute path to the maldet -a command,
but to change the current working directory from which you give the command.

For example, if you're in /home/ and you enter maldet -a
/home/user3/public_html and you get the error you specified, simply try to
change the directory you are in (let's say / or /usr ) and try again the
command maldet -a /home/user3/public_html/

Regards.

—
Reply to this email directly or view it on GitHub
#56 (comment)
.

from linux-malware-detect.

version 1.5 has went stable and should address this issue, thank you for your feedback.

from linux-malware-detect.