5. Important NOD32LFS/NOD32BFSMechanisms ....19 otherwise without a permission in writing from the 5.1. User Specific Configuration ..........20 author. Eset, s.r.o. reserves the right to change any 5.2. Handle Object Policy ............20 of the described application software without prior 5.3.
Page 4
Dear user, you have acquired NOD32 for Linux/BSD File Server - NOD32LFS/NOD32BFS - probably the best anti- virus system running under the Linux/BSD OS. As you will soon find out, the system using, the state-of-the-artNOD32 scanning engine, has unsurpassed scanning speed and detection rate, combined with a very small footprint that makes it the ideal choice for any Linux/BSD OS server.
Page 6
RedHat Ready and Novell (SuSE) Ready certificate. This means in particular that the package is installed as an add-on application, i.e. the primary installation directory is ’/opt/eset/nod32’ instead of the base Linux OS directory structure. However, there are more differences between the original and ’Ready’ variation of the product that are beyond the scope of this document.
Page 8
Once the product package has been successfully installed, it is time to become familiar with its content. The structure of the NOD32LFS/NOD32BFS is shown in the figure 3-1. The system is composed of the following components. Figure 3-1. Structure of NOD3LFS/NOD3BFS. CORE AGENTS nod32d...
Page 9
Note that in case of RedHat Ready and Novell (SuSE) Ready variation of the NOD32 for Linux Mail Server the configuration and authorization directory is /etc/opt/eset/nod32 The directory consists of the following files. nod32.cfg This is the most important configuration file as it maintains the major part of the product functionality. For this reason the file is further referred to as ‘main configuration file‘...
Note that in Linux RedHat Ready and Novell (SuSE) Ready variation of the product an appropriate command line will look as follows. 0 3 * * * /opt/eset/nod32/sbin/nod32 [option(s)] INCL_SCAN_DIR \ -- -EXCL_SCAN_DIR Please note that there is no configuration file interface supported for this module.
of the NOD32LFS/NOD32BFS product and thus it must be compiled and installed into the kernel prior the NOD32 on- access scanner (nod32dac daemon) initialization. On the other hand the Dazuko technique make on-access scanning independent of used file system type. It is also suitable for controlling file system objects via Network File System (NFS), Nettalk and Samba.
4.2.1.2. Installation and configuration It has been already discussed that prior any ‘nod32dac’ initialization, so-called Dazuko kernel module has to be compiled and installed within the running kernel. Note that the following text contains only brief description of the Dazuko kernel module installation. Therefore it is highly recommended to read the Dazuko how-to-install documentation (see http://www.dazuko.org/howto-install.shtml) in order to compile and load the Dazuko module properly into the kernel.
/sbin/kldstat In all cases there should be Dazuko listed in the output of these commands. Unless the device node is created automatically, create it with: mknod -m 600 /dev/dazuko c $(grep dazuko /proc/devices | sed “s/ .*//“) 0 chown root:root /dev/dazuko resp.
4.2.2.1. Operation principle On-access scanner ‘libnod32pac.so’ (NOD32 Preload library based file Access Controller) is a shared objects library that is used as a preload library of LIBC and can become functional during the system start-up. It is thus applicable for file system servers using LIBC calls, for instance ftp server, Samba server etc.
Page 17
responsible for initialization of smbd daemon by the following line LD_PRELOAD=/usr/lib/libnod32pac.so daemon /usr/sbin/smbd $SMBDOPTIONS In this manner selected file system objects controlled by Samba will be checked immediately after Samba initialization, i.e. during the system start-up. chapter 4 / Integration with Linux/BSD File System...
5.1. User Specific Configuration User Specific Configuration mechanism is implemented in the product in order to provide user with enhanced configuration functionality. It allows to define NOD32 anti-virus scanner parameters selectively for user accessing file system objects. Please note that the detailed description of this functionality can be found in nod32.cfg(5) manual page and manual pages referenced there.
configuration option (‘av_enabled‘). For detailed information on these configuration options, please refer to the nod32. cfg(5) manual page. Figure 5-1. Scheme of Handle Object Policy mechanism. action_on_processed object not accepted accept defer, discard, reject av_enabled action_on_infected action_on_uncleanable action_on_notscanned accept defer, discard, reject object not accepted object accepted Every object processed by NOD32LFS/NOD32BFS is at first handled with respect to the setting of the configuration...
6.1.1. NOD32 mirror creation First, the mirror of all relevant so-called NOD32 precompiled modules have to be created from the origin ESET server(s). In the product developed for Linux OS and BSD OS the precompiled NOD32 modules introduced above are...
(defined by EDITOR environment variable). Similar command is valid for Linux RedHat Ready and Linux Novell (SuSE) Ready product 0 * * * * /opt/eset/nod32/sbin/nod32_update chapter 6 / NOD32 system update and maintenance...
Page 28
Therefore, in case of bugs or inconsistencies found within this documentation, please report a problem to our support center http://www.eset.com/support We are looking forward to help you solve any problem concerning the product.
Need help?
Do you have a question about the NOD32 ANTIVIRUS - FOR LINUX-BSD FILE SERVER and is the answer not in the manual?
Questions and answers