ESET MAIL SECURITY, Installation Manual

Page: 28 / 42

28
ESET Mail Security
7.1. ESETS update utility
To maintain the effectiveness of ESET File Security, the virus signature database must be kept
up to date. The esets_update utility has been developed for this purpose (see the esets_update(8)
man page for details). To launch an update, the configuration options ‘av_update_username‘ and
‘av_update_password‘ must be defined in the [global] section of the ESETS configuration file.
In the event that your server accesses the Internet via HTTP proxy, the additional configuration
options ‘proxy_addr‘, ‘proxy_port‘ must be defined. If access to the HTTP proxy requires a
username and password, the ‘proxy_username‘ and ‘proxy_password‘ options must also be
defined in this section. To initiate an update, enter the following command:
@SBINDIR@ /esets_update
To provide the highest possible security for the end user, the ESET team continuously collects
virus definitions from all over the world–new patterns can appear within the virus signature
database in very short intervals. For this reason, we recommend that updates be initiated on a
regular basis. To specify the update frequency, the ‘av_update_period‘ option must be defined in
the [global] section of the ESETS configuration file. The ESETS daemon must be up and running
in order to successfully update the virus signature database.
7.2. ESETS update process description
The update process consists of two stages: First, the precompiled update modules are
downloaded from the ESET server. If the option ‘av_mirror_enabled‘ is present in the [global]
section of the ESETS configuration file, copies (or mirror) of these update modules are created
in the following directory:
@BASEDIR@ /mirror
If desired, the Mirror directory path can be redefined using the ‘av_mirror_dir‘ option in the
[update] section of the ESETS configuration file. The newly created Mirror thus serves as a fully
functional update server and can be used to create lower (child) Mirrors. However, the following
conditions must be fulfilled . First, there must be an HTTP server installed on the lower computer
where the modules will be downloaded from. Second, the update modules to be downloaded by
other computers must be placed in the following directory:
/http-serv-base-path/eset_upd
In the line above, ‘http-serv-base-path‘ is a base HTTP server directory path–this is the first
place the update utility will search for update modules.
The second stage of the update process is the compilation of modules loadable by the ESET
Mail Security scanner from 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. The modules are created in the following directory:
@BASEDIR@
This is the directory where the ESETS daemon loads modules from and thus can be redefined
using the ‘base_dir‘ option in the [global] section of the ESETS configuration file.