Go to file
Sérgio M. Basto f02bd6b37a Also fix type of clamav-milter.service 2018-01-17 20:49:23 +00:00
.gitignore Update main.cvd, daily.cvd and bytecode.cvd 2018-01-09 00:29:41 +00:00
586a5180287262070637c8943f2f7efd652e4a2c.patch Security fixes CVE-2017-6420 (#1483910), CVE-2017-6419 (#1483909), 2018-01-11 03:18:45 +00:00
60671e3deb1df6c626e5c7e13752c2eec1649f98.patch fix unit tests 2018-01-11 20:52:57 +00:00
ChangeLog-rpm.old - updated to 0.96.1 2010-06-01 19:22:07 +00:00
Makefile readded makefile 2010-08-11 10:01:44 +02:00
README.fedora removed stanza from upstart script which waited for 'starting\ XXX'; 2009-11-22 10:47:16 +00:00
clamav-0.98-umask.patch Upgrade to 0.98 and updated main.cvd and daily.cvd (#1010168) 2013-10-06 22:07:29 +02:00
clamav-0.99-private.patch Upgrade to 0.99 and updated daily.cvd (#1287327) 2015-12-02 01:46:49 +01:00
clamav-0.99.1-setsebool.patch - Upgrade to 0.99.1 and updated main.cvd and daily.cvd (#1314115) 2016-03-29 23:41:07 +02:00
clamav-0.99.2-temp-cleanup.patch Backported upstream patch to unbreak e2guardian vs. temp files 2017-11-26 03:46:38 +01:00
clamav-milter.systemd Also fix type of clamav-milter.service 2018-01-17 20:49:23 +00:00
clamav-milter.sysv Update to 0.99.2 2016-06-13 11:36:38 -06:00
clamav-milter.upstart Update to 0.99.2 2016-06-13 11:36:38 -06:00
clamav-notify-servers Try fix rhbz #1473642 2017-09-15 19:25:16 +01:00
clamav-update.crond Upgrade to 0.97.8 2013-05-04 19:50:36 -05:00
clamav-update.logrotate auto-import changelog data from clamav-0.71-0.fdr.2.rh80.src.rpm 2004-11-08 04:10:52 +00:00
clamav.spec Also fix type of clamav-milter.service 2018-01-17 20:49:23 +00:00
clamd-README Update README 2014-01-29 14:57:40 -06:00
clamd-gen merged with F-8 2008-01-01 13:19:16 +00:00
clamd-wrapper fixed signal specifier in clamd-wrapper (#668131) 2011-01-08 10:47:53 +01:00
clamd.SERVICE.init lowered stop priority of sysv initscripts (#629435) 2010-09-29 09:49:53 +02:00
clamd.logrotate Also send logrotate script stdout to /dev/null (bug #1376815) 2016-10-18 14:20:42 -06:00
clamd.scan.upstart Update to 0.99.2 2016-06-13 11:36:38 -06:00
clamd.sysconfig auto-import changelog data from clamav-0.71-0.fdr.2.rh80.src.rpm 2004-11-08 04:10:52 +00:00
clamd@.service Yet another fix for clamd@ service 2018-01-17 17:20:04 +00:00
clamd@scan.service made script in -scanner-systemd an instance of clamd@.service 2012-01-08 12:55:35 +01:00
dfc00cd3301a42b571454b51a6102eecf58407bc.patch Security fixes CVE-2017-6420 (#1483910), CVE-2017-6419 (#1483909), 2018-01-11 03:18:45 +00:00
fa15aa98c7d5e1d8fc22e818ebd089f2e53ebe1d.diff Add patch for openssl-1.1 2017-07-17 15:54:01 +01:00
freshclam-sleep merged with F-8 2008-01-01 13:19:16 +00:00
freshclam.sysconfig Allow freshclam to run automatically on install (bug #1408649) 2017-03-26 15:55:01 -06:00
llvm-glibc.patch fixed build with recent gcc/glibc toolchain 2012-02-05 13:02:29 +01:00
sources Update main.cvd, daily.cvd and bytecode.cvd 2018-01-09 00:29:41 +00:00

README.fedora

A clamav-milter setup consists of the following three components:

* the clamav-milter itself

  --> this is provided by the 'clamav-milter' package plus (alternatively)
      'clamav-milter-upstart' or 'clamav-milter-sysvinit'

  The main configuration is in /etc/mail/clamav-milter.conf and MUST
  be changed before first use.

  The -sysvinit package is managed by the traditional tools, but
  -upstart requires modification of /etc/event.d/clamav-milter to
  enable automatic startup.  See comments there for more details.

* a clamav scanner daemon

  --> this package is called 'clamav-scanner' plus (alternatively)
      'clamav-scanner-upstart' or 'clamav-scanner-sysvinit'

  The daemon is configured by /etc/clamd.d/scan.conf (which MUST be
  edited before first use).

  The -sysvinit package is managed by the traditional tools, but
  -upstart requires modification of /etc/event.d/clamd.scan to enable
  automatic startup.  See comments there for more details.

* the MTA (sendmail/postfix)

  --> you should know how to install this...

  When communicating across unix sockets with the clamav-milter, it is
  suggested to use the /var/run/clamav-milter/clamav-milter.socket
  path.  You have to add something like

    INPUT_MAIL_FILTER(`clamav', `S=local:/var/run/clamav-milter/clamav-milter.socket, F=, T=S:4m;R:4m')dnl

  to your sendmail.mc.



It is suggested that components communicate through TCP sockets as
this eases setup.  Please add corresponding packet filter rules!


EXAMPLE
=======

For clamav-milter, a possible setup might be created by

A)  On the MTA  (assumed hostname 'host-mta')

  1. Add to sendmail.mc

    | INPUT_MAIL_FILTER(`clamav', `S=inet:6666@host-milter, F=, T=S:4m;R:4m')dnl

  2. Rebuild sendmail.cf


B)  On the clamav-milter host (assumed hostname 'host-milter')

  1. Install clamav-milter + clamav-milter-upstart packages

  2. Set in /etc/mail/clamav-milter.conf

    | MilterSocket	inet:6666
    | ClamdSocket	tcp:host-scanner:6665

     and all the other options which are required on your system

  3. Edit /etc/event.d/clamav-milter and uncomment the

    | start on starting local

     line. Restart your system or execute

    | initctl emit starting local

  4. Add something like

    | iptables -N IN-cmilt
    | iptables -A IN-cmilt -s host-mta -j ACCEPT
    | iptables -A IN-cmilt -j DROP

    | iptables -A INPUT -p tcp --dport 6666 -j IN-cmilt

     to your firewall setup

C)  On the clamav-scanner host (assumed hostname 'host-scanner')

  1. Install clamav-scanner + clamav-scanner-upstart packages

  2. Add to /etc/clamd.d/scan.conf

    | TCPSocket 6665
    | TCPAddr   host-scanner

     comment out possible 'LocalSocket' lines and set all the other
     options which are required on your system

  3. Edit /etc/event.d/clamav-scanner and uncomment the

    | start on starting local

     line. Restart your system or execute

    | initctl emit starting local

  4. Add something like

    | iptables -N IN-cscan
    | iptables -A IN-cscan -s host-milter -j ACCEPT
    | iptables -A IN-cscan -j DROP

    | iptables -A INPUT -p tcp --dport 6665 -j IN-csan

     to your firewall setup