ESET GATEWAY SECURITY, Installation Manual

Page: 30 / 38

30 ESET Gateway Security
7.1. ESETS update utility
In order to keep the ESET Gateway Security effective, it is necessary to keep its virus
signatures database up to date. The esets_update utility has been developed for this purpose
(see esets_update(8) manual page for details). In order to launch update one has to define
configuration options ‘av_update_username‘ and ‘av_update_password‘ in [global] section of
ESETS configuration file. Note that in case you access the Internet via HTTP proxy additional
configuration options ‘proxy_addr‘, ‘proxy_port‘ and optionally ‘proxy_username‘ and ‘proxy_
password‘ have to be specified there as well. To trigger an update, enter command:
@SBINDIR@ /esets_update
To provide the highest security for the user, the ESET team collects the virus definitions
continuously from all over the world. The new patterns can appear within the database in very
short intervals. It is therefore recommended, to trigger an update on a regular basis. Note that
ESETS daemon is able to provide the periodic update of the system once ‘av_update_period‘
configuration option specified in [global] section of ESETS configuration file and the daemon is
up and running.
7.2. ESETS update process description
The update process is composed of two stages. First, the so called pre-compiled modules are
downloaded from the origin ESET server. If configuration option ‘av_mirror_enabled‘ is enabled
in section [global] of ESETS configuration file, the mirror of these modules is created in directory
@BASEDIR@ /mirror
Note that the mirror directory path can be redefined using configuration option ‘av_mirror_
dir‘ in section [update] of ESETS configuration file. The newly created mirror thus serves as fully
functional modules download server and can be used to create subordinate mirrors, however,
some more conditions have to be fulfilled yet. First, there must be a http server installed on the
computer where the modules are going to be downloaded from. Second, the modules to be
downloaded by other computers have to be placed at the directory path
/http-serv-base-path/eset_upd
where ‘http-serv-base-path‘ is a base http server directory path, as this is the first place where
update utility looks the modules for.
Second part of the update process is the compilation of modules loadable by the ESET Gateway
Security scanner from those stored in the local mirror. Typically the following ESETS loading
modules are created: loader module (em000.dat), scanner module (em001.dat), virus signature
database module (em002.dat), archives support module (em003.dat), advanced heuristics
module (em004.dat), etc. in the directory:
@BASEDIR@
Note that it is exactly the directory where ESETS daemon loads modules from and thus can
be redefined by using configuration option ‘base_dir‘ in section [global] of ESETS configuration
file.