|
The emulation of the clamd interface makes it possible to integrate Dr.Web ClamD with external applications capable to connect to the clamd anti-virus daemon (included in ClamAV).
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: https://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.havp.org/documentation/
|
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.
Example of how to connect HAVP to Dr.Web ClamD:
1.Configuring Dr.Web ClamD:
[ClamD]
Start = yes
[ClamD.Endpoint.proxy]
ClamdSocket = /var/run/drweb.clamd
|
2.Configuring HAVP:
ENABLECLAMD true
CLAMDSOCKET /var/run/drweb.clamd
|
Settings that configure connections to any other anti-virus products (ENABLE* parameters) must be set to false.
|