b77bb64a6a
apply a fix for a 5 month old and solved security issue. Please fill
your comments at
https://bugzilla.redhat.com/beta/show_bug.cgi?id=131385
- added 'BuildRequires: bc' (should work without also, but ./configure
gives out ugly warnings else)
0.81-0.fdr.1
- updated to 0.81
- do not ship the 'clamd.milter' daemon anymore; clamav-milter supports an
internal mode now which is enabled by default
- updated -milter %%description
0.80-0.fdr.2
- s!cron.d/clamav!cron.d/clamav-update! in the %%description of the -update
subpackage (https://bugzilla.fedora.us/show_bug.cgi?id=1715#c39)
0.80-0.fdr.1
- updated to 0.80
- removed DMS, FreeBSD-HOWTO and localized docs as it is not shipped
anymore
- buildrequire 'curl-devel'
- renamed clamav.conf to clamd.conf (upstream change)
- updated -initoff patch
0.75.1-0.fdr.1
- updated to 0.75.1
- use %%configure, the problems with the architecture specification seem to
have passed (probably because of an autoconf update)
- set mode 0600 for the cron-script (required by vixie-cron)
- made the cronjob a spambot and send mail about deactivated freshclam
service to nearly everybody... (root, postmaster, webmaster)
- other fixes in the notification cronjob
0.75-0.fdr.1
- updated to 0.75
0.74-0.fdr.2
- moved /usr/bin/clamav-config from main into -devel
0.74-0.fdr.1
- updated to 0.74
0.73-0.fdr.1
- updated to 0.73
- added pkgconfig file
0.72-0.fdr.3
- notify the user about a deactivated clamav-update service
- added clamd-gen script which generates template spec-files for services
using clamd
- copied template configuration files to %pkgdatadir/template (needed for
clamd-gen)
- moved the clamd-wrapper from %_initrddir to %{pkgdatadir}; a symlink will
be provided for compatibility reasons
- conditionalized building of the -milter subpackage ('--without milter'
switch) to enable builds on RH73 (bug #1715, comment #5/#7)
0.72-0.fdr.2
- removed 'BuildRequires: dietlibc'; it was a leftover from the
pre-use-signal era (before 0.70) (bug #1716)
0.72-0.fdr.1
- updated to 0.72
59 lines
1.9 KiB
Plaintext
59 lines
1.9 KiB
Plaintext
To create individual clamd-instance take the following files and
|
|
modify/copy them in the suggested way:
|
|
|
|
clamd.conf:
|
|
* set LogFile, PidFile, LocalSocket and User to suitable values
|
|
* place this file into /etc/clamd.d with a unique service-name;
|
|
e.g. as /etc/clamd.d/<SERVICE>.conf
|
|
|
|
To make logfile rotation work properly, the LogFile should be
|
|
writable for the assigned User. Recommended way to reach this, is
|
|
to:
|
|
* make it owned by the User's *group*
|
|
* assign at least 0620 (u+rw,g+w) permissions
|
|
|
|
A suitable command might be
|
|
| # touch <logfile>
|
|
| # chgrp <user> <logfile>
|
|
| # chmod 0620 <logfile>
|
|
|
|
NEVER use 'clamav' as the user since he can modify the database.
|
|
This is the user who is running the application; e.g. for mimedefang
|
|
(http://www.roaringpenguin.com/mimedefang), the user might be
|
|
'defang'.Theoretically, distinct users could be used, but it must be
|
|
made sure that the application-user can write into the socket-file,
|
|
and that the clamd-user can access the files asked by the
|
|
application to be checked.
|
|
|
|
|
|
clamd.logrotate:
|
|
* set the correct value for the logfile
|
|
* place it into /etc/logrotate.d
|
|
|
|
clamd.sysconfig:
|
|
* set the name of the config-file and the local socket
|
|
* copy it to /etc/sysconfig/clamd.<SERVICE>
|
|
|
|
clamd.init:
|
|
* set the service-name
|
|
* place it into /etc/init.d/ with an unique name and activate it
|
|
(e.g. with /sbin/chkconfig clamd.<SERVICE> on)
|
|
|
|
Additionally, a symlink must be set to clamd in a way like
|
|
| # ln -s clamd /usr/sbin/clamd.<SERVICE>
|
|
and the directory for the socket file must be created (see 'LocalSocket'
|
|
in clamd.conf)
|
|
| # mkdir -p /var/run/clamd.<SERVICE>
|
|
|
|
|
|
This directory must be writable by the 'User' chosen in the config-file.
|
|
|
|
|
|
|
|
[Disclaimer:
|
|
this file and the script/configfiles are not part of the official
|
|
clamav package.
|
|
|
|
Please send complaints and comments to
|
|
mailto:enrico.scholz@informatik.tu-chemnitz.de!]
|