In this section
▫Remote file scanning (Engine)
▫Sending files for scanning (File)
Dr.Web MeshD is a mediator that ensures interaction of a host with Dr.Web Server Security Suite installed and other cloud hosts.
Dr.Web MeshD uses the following connection types:
•Client (service)—used by Dr.Web MeshD to connect to other cloud hosts that are clients of services provided by the given host.
|
Dr.Web Server Security Suite components operating on the host and using services provided by the cloud connect to Dr.Web MeshD, which operates on the same host, through a local Unix socket. At that, a client connection is not used. |
•Partner (peer to peer)—used by Dr.Web MeshD for interaction with peer (within a service) partner cloud hosts. Usually such horizontal connections are used for scaling and distributing the load when interacting with the cloud, as well as for synchronization of cloud hosts.
•Uplink—used by Dr.Web MeshD for connecting this host as a client to cloud hosts that provide services (for example, sending files for scanning and so on).
The use of all three types of connections is configured for different cloud services independently from each other. At that, the same host can be configured as a server for processing client requests within one service (for example, checking URLs) and as a client within another service (for example, remote file scanning).
Within cloud, hosts perform authorized interaction via SSH, that is, all sides of interhost communication are always mutually authenticated. For the authentication, host keys are used in compliance with RFC 4251 
. A client connection from a local component is always considered as trusted.
Dr.Web MeshD can either operate in daemon mode or run at the request of other Dr.Web Server Security Suite components installed on the local host. If Dr.Web MeshD is configured to serve client connections (the ListenAddress parameter is not empty) and at least one of the services is activated, Dr.Web MeshD starts as a daemon and awaits client connections.
If Dr.Web MeshD is not set to process client connections (the ListenAddress parameter is empty) and there are no requests to this component during a time interval specified by the IdleTimeLimit parameter, the component shuts down automatically.
This service allows to use Dr.Web Scanning Engine for scanning remote files: hosts acting as clients send files for scanning to a server host, and server hosts provide a service for scanning files sent by the client hosts. Typical client settings are as follows:
… |
The following settings are specified on the host acting as a local scanning server:
EngineChannel = On |
Here, <server address> in the uplink connection of the client must refer to the <address> and <port> that are used by the server host for managing client connections.
Sending files for scanning (File)
This feature is not used (remote scanning is provided by the Engine service).
This service allows to check whether a URL belongs to potentially dangerous and unwanted categories: client hosts send a URL to be checked to a server host. Typical client settings are as follows:
… |
The following settings are specified on the host acting as a URL checking server:
UrlChannel = On |
Here, <server address> in the uplink connection of the client must refer to the <address> and <port> that are used by the server host for managing client connections.