[Bug 571543] Re: Milter and Freshclam configurations buggy in Lucid

[Scott Kitterman]

** Description changed:

  Binary package hint: clamav
  
  In the default configuration, logrotate for clamav-milter will cause
  incorrect permissions.
  
  In the default configuration, the new bytecode anti-virus checks were
  inadvertently left disabled.
+ 
+ By default, clamav-daemon will restart every six hours to pick up new
+ signatures.  There is an off by default feature for freshclam to notify
+ clamav-daemon when it's restarted to enable immediate use of new
+ signatures.  This is supposed to be controlled by a debconf boolean, but
+ the path to the clamd config file is stored instead.
  
  
  TEST CASE:
  
  For clamav-milter, with the current package installed, inspect the
  contents of /etc/logrotate.d/clamav-milter and find that the create line
  only includes the group permissions, not the user (clamav):  "create 640
  adm".  Install the updated packages and check the file again and find
  that it now includes user too: "create 640  clamav adm".
  
  For the freshclam bytcode issue, inspect /etc/clamav/freshclam.conf and
  note the absence of a Bytecode parameter.  Install the updated packages
  and see that freshclam.conf now contains "Bytecode true" (or false if
  the user has set it to false previously).
+ 
+ Use dpkg-reconfigure clamav-freshclam and say change the "Should clamav
+ daemone be notified of updates" question to yes.  Inspect
+ /var/cache/debconf/config.dat and find the paramete for clamav-
+ freshclam/NotifyClamd and note the value.  It should say
+ "/etc/clamav/clamd.conf".  Install the updated packages and then inspect
+ the same value again.  It should say "true".

-- 
Milter and Freshclam configurations buggy in Lucid
https://bugs.launchpad.net/bugs/571543
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in ubuntu.