Installation manual

11
6. Integration with File System services
This chapter describes the On-demand and On-access scanner configuration which will provide the most effective protection
from virus and worm file system infections. ESET File Security’s scanning power is derived from the On-demand scanner
command ‘esets_scan’ and the On-access scanner command ‘esets_dac’. The Linux version of ESET File Security offers an
additional On-access scanner technique which uses the preloaded library module libesets_pac.so. All of these commands are
described in the following sections.
6.1 On-demand scanner
The On-demand scanner can be started by a privileged user (usually a system administrator) through the command line
interface, web interface or by the operating system’s automatic scheduling tool (e.g., cron). The term On-demand refers to file
system objects which are scanned on user or system demand.
The On-demand scanner does not require special configuration in order to run. After the ESETS package has been properly
installed and a valid license has been moved to the license keys directory (@ETCDIR@/license), the On-demand scanner can be
run immediately using the command line interface or the Scheduler tool. To run the On-demand scanner from the command line,
use the following syntax:
@SBINDIR@/esets_scan [option(s)] FILES
where FILES is a list of directories and/or files to be scanned.
Multiple command line options are available using ESETS On-demand scanner. To see the full list of options, please see the
esets_scan(8) man page.
6.2 On-access scanner using preload LIBC library
The On-access scanner is invoked by user(s) access and/or operating system access to file system objects. This also explains the
term On-access; the scanner is triggered on any attempt to access a selected file system object.
In the following sections, we will also describe the integration of the On-access scanner powered by Dazuko with Linux/BSD file
system services. Using Dazuko may not be feasible in all situations, including system administrators who maintain critical
systems where:
the source code and/or configuration files related to the running kernel are not available,
the kernel is more monolithic than modular,
the Dazuko module simply does not support the given OS.
In any of these cases, the On-access scanning technique based on the preload LIBC library should be used. See the following
topics in this section for detailed information. Please note that this section is relevant only for Linux OS users and contains
information regarding the operation, installation and configuration of the On-access scanner using the preload library
‘libesets_pac.so’.
6.2.1 Operation principle
The On-access scanner libesets_pac.so (ESETS Preload library based file Access Controller) is a shared objects library which is
activated at system start up. This library is used for LIBC calls by file system servers such as FTP server, Samba server etc. Every
file system object is scanned based on customizable file access event types. The following event types are supported by the
current version:
Open events
This file access type is activated if the word ‘open’ is present in the ‘event_mask’ parameter in the esest.cfg file ([pac] section).
Create (close) events
This file access type is activated if the word ‘create’ is present in the ‘event_mask’ parameter in the esets.cfg file ([pac] section). In
this case, all file descriptor and FILE stream create/close functions of the LIBC are intercepted.
Exec events
This file access type is activated if the word ‘exec’ is present in the ‘event_mask’ parameter in the esets.cfg ([pac] section). In this
case, all exec functions of the LIBC are intercepted.
All opened, closed and executed files are scanned by the ESETS daemon for viruses. Based on the result of such scans, access to
given files is denied or allowed.