Skip to content
Markus Strehle edited this page Nov 17, 2016 · 5 revisions

ClamSAP adapters

The OS project https://sourceforge.net/projects/clamsap/ provides 2 Virus Scan Adapters. The problem with this is, it often confuses the system administrators. Therefore I want provide a brief overview of what integration should be installed in which situation. ClamSAP provides the libraries:

1.(lib)clamsap.(shared)

This library is only a middleware interface to load directly the ClamAV shared library including the siguture files. This means, ClamAV must be installed on this system. The clamsap and clamav shared libraries must have the same platform architecture, e.g. Linux x64 clamav needs a x64 version of clamsap.

Check the availability of this with executing "clamscan", because this command uses libclamav.so.

2.(lib)clamdsap.(shared)

This library is a network connector the clamd (the ClamAV daemon). By default clamd only listen to localhost connections, however you can configure which hosts are allowed to connect also remote clamd processes. The daemon must be started first and you have to check if is accepts remote and/or only local host connections. The libclamdsap.so uses the default port 3310. See the setting of the daemon in /etc/clamd.conf.

Defaults in /etc/clamd.conf

TCPSocket 3310

TCPAddr 127.0.0.1

Check the availability of this with executing "clamdscan", because this command uses the daemon clamd.

For both integration you may first have to download the AV signature files. The daemon for this is freshclam. See /etc/freshclam.conf. Maybe you need a proxy within your organization, then uncomment

HTTPProxyServer proxy

HTTPProxyPort 8080

Clone this wiki locally