Integration with External Applications

The interface—that emulates the one of the clamd anti-virus daemon (included in ClamAV)—allows Dr.Web ClamD to communicate with any external application that is capable of connecting to this 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
Squid

Use of clamd:

Scanning of files received from the Internet.

Integration requirements:

Using squidclamav or HAVP as an intermediate component.

Links to documentation:

Squid documentation: http://www.squid-cache.org/Doc/

Description and source code files of squidclamav: http://squidclamav.darold.net/

HTTP proxy server which can perform anti-virus scans
HAVP

Use of clamd:

Scanning of files received from the Internet.

Integration requirements:

Configuring HAVP to use clamd for anti-virus scanning configuration:

ENABLECLAMD true
CLAMDSOCKET <path_to_clamd_UNIX_socket>

or (if TCP connection is used instead of a UNIX socket):

ENABLECLAMD true
CLAMDSERVER <IP>
CLAMDPORT <port>

where <path_to_clamd_UNIX_socket> or the <IP>:<port> pair corresponds to the socket of a connection point (endpoint) configured in Dr.Web ClamD.

Links to documentation:

HAVP documentation: http://www.server-side.de/documentation.htm

In the settings of the external software component that communicates directly with Dr.Web ClamD as with the clamd anti-virus daemon, specify an address for connecting to clamd as a path to a UNIX socket or as a TCP socket listened to by Dr.Web ClamD at one of its connection points (endpoint) set up in its configuration.

Settings that configure connections to any other anti-virus products ( ENABLE* parameters) must be set to false.