The emulation of the interface of the clamd anti-virus daemon included in the ClamAV anti-virus solution makes it possible to integrate Dr.Web ClamD with any external applications capable of connecting to the clamd anti-virus daemon.
The table below shows examples of applications that can use clamd for anti-virus scans:
Product |
Integration |
||
|---|---|---|---|
HTTP services |
|||
HTTP proxy server |
Use of clamd Scan files received from the internet. Integration requirements Use an intermediate component: squidclamav or HAVP. Links to documentation Squid Description and source code of squidclamav |
||
HTTP proxy server that can perform anti-virus scans |
Use of clamd Scan files received from the internet. Integration requirements Enable clamd for anti-virus scanning in the HAVP configuration file:
or (if a TCP connection is used instead of a Unix socket):
where <path_to_clamd_Unix_socket> or the <IP>:<port> pair corresponds to the socket of the endpoint configured in Dr.Web ClamD. Links to documentation HAVP |
||
In the settings of the external software component that communicates directly with Dr.Web ClamD as with the clamd anti-virus daemon, specify a path to a Unix socket or a TCP socket listened by Dr.Web ClamD at one of its endpoints set up in its configuration as an address for connecting to clamd.
Example of connecting HAVP to Dr.Web ClamD:
1.Dr.Web ClamD configuration:
[ClamD]
[ClamD.Endpoint.proxy] |
2.HAVP configuration:
ENABLECLAMD true |
Settings for connecting to other anti-virus products (ENABLE* parameters) must be set to false.