Home > NOD32 FAQ > Why does the file scan not indicate the presence of malware on a NSS volume?

Why does the file scan not indicate the presence of malware on a NSS volume?

February 16th, 2010 admin Leave a comment Go to comments

When scanning files with ESET File Security for Linux the scan detects no malware on a mounted NSS volume, even if present. Upon finishing, the scanner displays a list of scanned objects. Are some of the scanned objects infected, however, all items on the list will appear as clean.

The reason for this is that Novell Storage Services (NSS) distort common unix security principles the scanner relies on, limiting its privileges. This can result in threats not being detected on NSS mounted volumes.

To fix this problem:

Open the configuration file (with root permissions) in a text editor.
user@machine:~$ sudo nano /etc/esets/esets.cfg
[sudo] password for user:

Find the [global] section

Find the line:

esets_user = “esets”

and replace it by:

esets_user = “root”

Save the configuration file and exit.

Restart the esets_daemon.

NOTE: It is important to restart the ESETS daemon after saving the changes for the new settings to apply.

Categories: NOD32 FAQ Tags:
  1. No comments yet.
  1. No trackbacks yet.