The component is designed to establish connections to Doctor Web update servers to check for updates for virus databases and Dr.Web Virus-Finding Engine, for the database of web resource categories and for the anti-spam component. The lists of the servers that constitute an available update zone are stored in a special file signed to prevent its modification. Only basic and digest authentication are supported for connection to the update servers using a proxy server.
If Dr.Web Mail Security Suite is not connected to a centralized protection server or is connected to it in mobile mode, Dr.Web Updater is automatically started by the Dr.Web ConfigD configuration management daemon at intervals specified in the settings. The component can also be started by Dr.Web ConfigD upon receiving a corresponding command from the user (unscheduled update).
When updates become available on update servers, they are downloaded to the /var/opt/drweb.com/cache/ directory (for OSes of the GNU/Linux family) or /var/drweb.com/cache/ (for FreeBSD); after that they are moved to the working directories of Dr.Web Mail Security Suite.
By default, all updates are downloaded from the update zone that is common for all Dr.Web products. The list of the servers used by default and included in the update zone is specified in the files located in directories defined by *DrlDir parameters grouped by an update type: for virus databases and the scanning engine, for the database of web resource categories, for the antispam component). Upon a client request a custom update zone can be created (for each update type), the server list of which is specified in a separate file (named custom.drl by default) located in the directory specified by the corresponding *CustomDrlDir parameter. In this case, the update component will download updates only from these servers without using the servers from the default zone.
If you do not want to use the custom update zone, clear the value of the corresponding *CustomDrlDir parameter in the component settings.
|
The content of the files with server lists is signed so that the files cannot be modified. If you need to create a custom list of update servers, contact our technical support. |
The component can back up the files to be updated to further roll back updates at user request. You can specify a backup location and an update history depth in the component settings. To roll back updates, use the Dr.Web Ctl tool designed to manage Dr.Web Mail Security Suite from the command line (run the tool with the drweb-ctl command).
If Dr.Web Mail Security Suite is connected to a local cloud of Dr.Web for UNIX products and not connected to a centralized protection server, the Dr.Web Updater component is used to synchronize updates received by cloud hosts as well, that is, it sends latest updates received from update servers to the cloud and receives latest updates from the cloud, which allows to reduce the total load of Dr.Web update servers. This option can be enabled or disabled in the component settings.